On Jan 02 2017, Russ Allbery <r...@debian.org> wrote:
> Furthermore, it forces a rebased, clean representation of the patches,
> which I for one hugely prefer to the mess that you get if someone was
> packaging in Git and just randomly commits things directly to the
> packaging branch intermixed with merges from upstream. A few releases
> done that way will leave you almost completely unable to extract a rebased
> patch set against the current upstream source. (I have made this mistake
> so many times with my own packages.)
Have you tried to use git-debcherry in those situations? I have tried it
in some simpler cases and worked very well, but I'd be curious if anyone
has tried it on larger and more complex repositories.
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
