Bug#867214: git-buildpackage: Strange format of commit message added by import-orig

2017-07-05 Thread Robert Luberda
Guido Günther writes: > Using past tense was indeed a bad choice. I deliberately avoided the > terme "merge" here since we're not using the git merge machinery but > build the tree ourself (see --merge-mode in gbp-import-orig(1)). I used "merge" in my proposal, because technically the resulting

Bug#867214: git-buildpackage: Strange format of commit message added by import-orig

2017-07-04 Thread Guido Günther
On Tue, Jul 04, 2017 at 10:08:02PM +0200, Robert Luberda wrote: > Package: git-buildpackage > Version: 0.8.17 > Severity: normal > > Hi, > > gbp import-orig stared producing merge commit messages like > this one: > > > Updated version 20170702 from 'upstream/20170702' > > with Deb

Bug#867214: git-buildpackage: Strange format of commit message added by import-orig

2017-07-04 Thread Robert Luberda
Package: git-buildpackage Version: 0.8.17 Severity: normal Hi, gbp import-orig stared producing merge commit messages like this one: Updated version 20170702 from 'upstream/20170702' with Debian dir 43f841d7950f0587745d57c8c87fd79e1aed60dd which I don't really like for the three