Sean Whitton writes ("Bug#833025: dgit: quiltify smash strategy shouldn't fail
when current patch queue fails to apply"):
> I am the maintainer, but I think that there are use cases for a dgit
> quilt strategy that is essentially a one-shot single-debian-patch.
>
> Suppose that the package was team-maintained, such that introducing
> single-debian-patch would be disruptive -- perhaps because other team
> members expect to introduce new, separate patches in the future.
> However, for now there is only one patch, so a one-shot
> single-debian-patch is the easiest way to fix the quilt series after
> merging a new upstream version.
The real problem here is surely that it is "too hard" to work on the
patch series in git.
Since dgit needs to gateway between git and dpkg-source, it inevitably
ends up containing some pieces of a general version control system.
But I'm trying to avoid turning it into a general tool for patch stack
manipulation...
I do intend for dgit to, when generating synthetic history from a
non-dgit .dsc, produce a sort of patch stack representation.
> Ah, thanks for sharing this branch -- I knew you had some work going on
> but I didn't think it was published publicly.
You're welcome.
FTAOD, please don't actually _use_ that branch :-).
Ian.
--
Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
