Hi,
On Sun, Aug 12, 2018 at 02:07:43AM +0100, Ben Hutchings wrote:
> Control: tag -1 patch
>
> On Sun, 2018-08-12 at 00:28 +0100, Ben Hutchings wrote:
> > Control: reassign -1 git-buildpackage 0.9.9
> >
> > gbp pq is actually responsible for this.
> [...]
>
> I've written test cases and fixes
Control: reassign -1 git-buildpackage 0.9.9
Sorry, I see you already did this. Your first mail got duplicaed and
delayed by a disk problem on chiark...
Ian.
Control: reasssign -1 git-buildpackage
Ben Hutchings writes ("Bug#905934: git-debrebase: convert-from-gbp may lose
non-git header fields"):
> Package: git-debrebase
> Version: 6.6
> Severity: normal
>
> Where patches have DEP-3 header fields that cannot be directly i
Control: tag -1 patch
On Sun, 2018-08-12 at 00:28 +0100, Ben Hutchings wrote:
> Control: reassign -1 git-buildpackage 0.9.9
>
> gbp pq is actually responsible for this.
[...]
I've written test cases and fixes for this and a related bug, and
pushed them to:
Control: reassign -1 git-buildpackage 0.9.9
gbp pq is actually responsible for this.
Ben.
On Sat, 2018-08-11 at 23:48 +0100, Ben Hutchings wrote:
> Package: git-debrebase
> Version: 6.6
> Severity: normal
>
> Where patches have DEP-3 header fields that cannot be directly included
> in git
Package: git-debrebase
Version: 6.6
Severity: normal
Where patches have DEP-3 header fields that cannot be directly included
in git metadata, such as Origin, Forwarded, and Bug-Debian, they don't
seem to be reliably included in git commits.
For a real example, compare branches use-dgit (patch
6 matches
Mail list logo
