Hello, On Fri, Apr 20 2018, kact...@gnu.org wrote:
> [2018-04-19 10:14] Sean Whitton <spwhit...@spwhitton.name> >> Hello both, >> >> If Dmitry wants to continue to use dgit-maint-merge(7), using 3.0 >> (quilt) will not help. It will not introduce any additional >> metadata. The only change will be the addition of a patch header >> pointing to dgit-repos. > > What do you mean by 'additional metadata'? Patch headers generated > from git commits? I mean separated patches. >> Switching to dgit-maint-gbp(7) means using a patches-unapplied >> workflow. [...] > > I want to be able to do raw `dpkg-buildpackage`. I guess it means > patches-applied workflow, am I right. Basically yes. >> In the next month or so we (Ian Jackson and I) will be releasing a >> workflow called dgit-maint-debrebase(7) which >> >> - is patches-applied; but >> - automatically generates a perfect 3.0 (quilt) representation of the >> Debian changes. >> >> I.e. it should satisfy everyone. > > I am okay to wait for your next invention. Last one I remember -- > separate patches instead of single squashed patch in > dgit-maint-merge(7) was awesome. Sorry but I don't understand this last sentence. Perhaps you could rephrase. -- Sean Whitton
signature.asc
Description: PGP signature
