+1 for SCM compatibility. Since version control is a best practice for packaging IMHO, I think we should be able to apply those processes cleanly enough to let us continue with them. When we import patches from upstream, I think most adhere to some kind of format, what is standard is where the patch came From: and what's it's Subject:. When we export patches too. What I think is that an alias would do the work. Since I've been maintaining a patches branch just for adding metadata, given the fact I'm using tg2quilt, as many of us are, I think it's an unnecessary pain. That's only my considerations, but hope made a point.
On Mon, 2009-09-07 at 22:30 +0200, Raphael Hertzog wrote: > On Sat, 05 Sep 2009, Guido Günther wrote: > > I tried to point that out in June: > > http://lists.debian.org/debian-devel/2009/06/msg00551.html > > but failed. It'd be really helpful if DEP-3 would be compatible with the > > git format-patch output. > > Would it be helpful to say that From: can be an alias for Author: and > Subject: an alias for Description:? > > git format-patch alone will stil not be enough to generate a DEP3-compliant > header but would that resolve your concerns? > > Is that really better over (auto-)duplicating those fields when needed? > > Anyway, I'd rather wait some time until people have tried using this > format before deciding if we must make some special case due to > git format-patch. > > Cheers, > -- > Raphaël Hertzog > > -- Best regards, Adrian Perez <adrianperez....@gmail.com>
signature.asc
Description: This is a digitally signed message part
