Nikolaus Rath <nikol...@rath.org> writes: > 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. I haven't (in fact, hadn't heard of it). I've at this point redone all of my packages to export quilt series as the archive source format, so I no longer have a great test case for this. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
