Sean Whitton writes ("Re: Bug#852940: dgit: Feature or doc of workflow that
allows one to repeatedly amend patches in 3.0 (quilt) [and 1 more messages]"):
> On Sun, Jan 29, 2017 at 06:32:59PM +0000, Ian Jackson wrote:
> > > Could you explain how that would be the same as the 2nd option above,
> > > please? I don't follow.
> >
> > The different is that it would involve dgit doing it more
> > automatically.
>
> Ah, so when you said "split brain" you didn't mean patches-applied /
> patches-unapplied, but simply having two worktrees?
I meant dgit's "split brain" approach. This is used for other
distinctions besides patches applied/unapplied. With --quilt-dpm it's
used only for .gitignore, for example. (In the docs I call it "split
view" quilt mode and describe it as suitable for
"nearly-dgit-compatible" braches.)
Internally split view mode involves dgit's private working tree, but
dgit uses its private working tree for other things too. (The dgit
private working tree is not a `git worktree' working tree.)
See dgit(7) "SPLIT VIEW QUILT MODE" or search dgit(1) for "split" and
the part about --quilt=dpm etc.
Ian.
