Any progress on preserving DEP-3 fields, like Applied-Upstream or
Forwarded, when used before the description?
On Sun, 17 Oct 2010 15:08:56 +0200 Guido =?iso-8859-1?Q?G=FCnther?= <
a...@sigxcpu.org> wrote:
> On Sat, Oct 16, 2010 at 07:26:07PM +0200, Guido Günther wrote:
> > Hi David,
> > sorry for the late reply.
> >
> > On Tue, Oct 05, 2010 at 12:12:17AM -0300, David Bremner wrote:
> > > Package: git-build
On Sat, Oct 16, 2010 at 07:26:07PM +0200, Guido Günther wrote:
> Hi David,
> sorry for the late reply.
>
> On Tue, Oct 05, 2010 at 12:12:17AM -0300, David Bremner wrote:
> > Package: git-buildpackage
> > Version: 0.5.4
> > Severity: wishlist
> >
> > Currently gbp-import silently drops unknown hea
Hi David,
sorry for the late reply.
On Tue, Oct 05, 2010 at 12:12:17AM -0300, David Bremner wrote:
> Package: git-buildpackage
> Version: 0.5.4
> Severity: wishlist
>
> Currently gbp-import silently drops unknown header fields. This is
> problematic for the proposed DEP3 header, which allows more
Package: git-buildpackage
Version: 0.5.4
Severity: wishlist
Currently gbp-import silently drops unknown header fields. This is
problematic for the proposed DEP3 header, which allows more fields
than From, Date, and Subject. Minimally it should complain that
information loss is occuring. A nicer
5 matches
Mail list logo
