Sean Whitton writes ("Bug#852940: dgit: Feature or doc of workflow that allows
one to repeatedly amend patches in 3.0 (quilt)"):
> Or use 3.0 (quilt) with single-debian-patch and auto-commit, per
> dgit-maint-merge(7). That avoids the issue of representability.
No, because that would still generate a lot of annoying autogenerated
patch commits which you'd probably want to get rid of.
Sean Whitton writes ("Bug#852940: dgit: Feature or doc of workflow that allows
one to repeatedly amend patches in 3.0 (quilt)"):
> On Sat, Jan 28, 2017 at 11:56:09PM +0000, Ian Jackson wrote:
> > * Use a second git tree, and
> > 1st-tree$ git push ../2nd-tree +HEAD:t
> > 2nd-tree$ git checkout t~0 && dgit -wgf sbuild
...
> > Alternatively, it would be possible in principle for dgit to support a
> > split brain version of the existing non-split-brain quilt modes. That
> > would have the same effect as the 2nd option above. I'm not sure this
> > is a very good idea.
>
> 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.
Thanks,
Ian.
