How does git-debcherry cope with the overlapping changes when generating
debian/patches? What can you do if it fails to linearise the changes
(as, apparently, it may sometimes do)?
I am not sure this needs to be an issue. Or maybe I am just not seeing the problem correctly...
Where do I get git-debcherry from?
Would like to get a copy so I can prove my preconceived and fixed ideas on which one is better <grin>.^C^C^C^C^C^C^C
Would like to get a copy so I can understand some of these issues better myself.