On Sat, Oct 29, 2016 at 05:12:42PM +0100, Ian Jackson wrote: > > Feedback on dgit-nmu-simple(7) > > ============================== > > > > 1. Small patch to the third paragraph in my branch: s/maintainer's > > workflow/maintainer's git workflow/. > > > > 2. I can't see why the workflow wouldn't work for a new upstream > > version. Could you explain, either just to me or in the manpage? > > Well, the workflow as presented doesn't do anything to produce either > a new .orig or a git tree which contains appropriate information. And > what exactly that git tree's history should look like depends on the > maintainer's workflow. The part of the presented workflow that > updates debian/patches/* is implicit in dgit -wgf push.
I missed replying to this. If you merged an upstream version and generated a corresponding orig.tar, how could this be disruptive to the maintainer? Is that issue that dgit can't automatically refresh patches, and it would end up adding a messy patch to the end of the queue to represent the refreshing? -- Sean Whitton
signature.asc
Description: PGP signature
