On Wed, Sep 09, 2009 at 07:48:18PM +0200, Pierre Habouzit wrote:
> On Wed, Sep 09, 2009 at 08:50:34AM -0500, Manoj Srivastava wrote:
> > Seems to me that we have a widely used convention (which might
> > not be universal) that will meet our needs, and at least seems
> > compatible with a
On Wed, Sep 09, 2009 at 08:50:34AM -0500, Manoj Srivastava wrote:
> Seems to me that we have a widely used convention (which might
> not be universal) that will meet our needs, and at least seems
> compatible with a lot of software under distributed version control. I
> think it well be
On Tue, Sep 08 2009, Ben Finney wrote:
> Paul Wise writes:
>> What format do the other DVCS systems use for patch export?
>
> Bazaar users generate a “merge directive” for serialising a change set
> http://bazaar-vcs.org/MergeDirective>. The merge directive is
> metadata to be read by the ‘bzr m
Paul Wise writes:
> On Tue, Sep 8, 2009 at 7:53 AM, Pierre Habouzit wrote:
> > On Mon, Sep 07, 2009 at 10:30:14PM +0200, Raphael Hertzog wrote:
> >> 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
On Tue, Sep 08, 2009 at 03:23:50PM +0800, Paul Wise wrote:
> On Tue, Sep 8, 2009 at 7:53 AM, Pierre Habouzit wrote:
> > On Mon, Sep 07, 2009 at 10:30:14PM +0200, Raphael Hertzog wrote:
> >> Anyway, I'd rather wait some time until people have tried using this
> >> format before deciding if we must
On Tue, Sep 8, 2009 at 7:53 AM, Pierre Habouzit wrote:
> On Mon, Sep 07, 2009 at 10:30:14PM +0200, Raphael Hertzog wrote:
>> 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.
>
> It's not a s
On Mon, Sep 07 2009, Pierre Habouzit wrote:
> On Mon, Sep 07, 2009 at 10:30:14PM +0200, Raphael Hertzog wrote:
>> git format-patch alone will stil not be enough to generate a DEP3-compliant
>> header but would that resolve your concerns?
>
> It will be compatible if you relax the use of headers t
On Mon, Sep 07, 2009 at 10:30:14PM +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 fo
Julien Cristau a écrit :
> FWIW, I'm not going to use something that I can't produce with git
> format-patch and feed to git send-email / git am since that feels like
> busy work; in particular the Author and Description fields are not
> needed given there's From and Subject with the same informati
+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 pa
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 f
On Tue, Sep 01, 2009 at 07:32:55PM +0200, Julien Cristau wrote:
> On Wed, Aug 26, 2009 at 01:56:35 +0200, Raphael Hertzog wrote:
>
> > Hello,
> >
> > I made some last changes to the DEP following round 4. You'll find them
> > below.
> > I plan to switch the DEP's status to CANDIDATE since it's a
On Wed, Sep 2, 2009 at 09:22:30 +0200, Raphael Hertzog wrote:
> Are those patches in that format because you took them from the upstream
> git repository or because using this format from the start lets upstream
> pick it up easily?
>
Both (usually the latter though, because for patches which ar
On Tue, 01 Sep 2009, Julien Cristau wrote:
> On Wed, Aug 26, 2009 at 01:56:35 +0200, Raphael Hertzog wrote:
> > Current version: http://dep.debian.net/deps/dep3/
>
> FWIW, I'm not going to use something that I can't produce with git
> format-patch and feed to git send-email / git am since that fe
On Tue, Sep 1, 2009 at 17:21:28 -0400, Felipe Sateler wrote:
> Julien Cristau wrote:
>
> > FWIW, I'm not going to use something that I can't produce with git
> > format-patch and feed to git send-email / git am since that feels like
> > busy work; in particular the Author and Description fields
Julien Cristau wrote:
> On Wed, Aug 26, 2009 at 01:56:35 +0200, Raphael Hertzog wrote:
>
>> Hello,
>>
>> I made some last changes to the DEP following round 4. You'll find them
>> below. I plan to switch the DEP's status to CANDIDATE since it's about
>> time to start using this new format to try
On Wed, Aug 26, 2009 at 01:56:35 +0200, Raphael Hertzog wrote:
> Hello,
>
> I made some last changes to the DEP following round 4. You'll find them below.
> I plan to switch the DEP's status to CANDIDATE since it's about time to start
> using this new format to try it out. Once I've done this, I'
On Thu, Aug 27, 2009 at 01:23:40PM +0800, Paul Wise wrote:
> On Thu, Aug 27, 2009 at 1:14 AM, gregor herrmann wrote:
> > On Wed, 26 Aug 2009 10:13:58 +0200, Raphael Hertzog wrote:
> >
> >> On Wed, 26 Aug 2009, Ben Finney wrote:
> >> > I think that either of ‘Origin: vendor’ (for a patch created by
On Thu, 27 Aug 2009, Paul Wise wrote:
> On Thu, Aug 27, 2009 at 1:14 AM, gregor herrmann wrote:
> > I prefer to omit Origin and interpret a
> > missing-Origin-with-Author-present as a Debian patch.
> >
> > Adding a URL (pointing where - to a webinterface of a VCS?) seems
> > cumbersome, and just st
On Thu, Aug 27, 2009 at 1:14 AM, gregor herrmann wrote:
> On Wed, 26 Aug 2009 10:13:58 +0200, Raphael Hertzog wrote:
>
>> On Wed, 26 Aug 2009, Ben Finney wrote:
>> > I think that either of ‘Origin: vendor’ (for a patch created by the
>> > package maintainer) or ‘Origin: other’ would be better than
On Wed, 26 Aug 2009 10:13:58 +0200, Raphael Hertzog wrote:
> On Wed, 26 Aug 2009, Ben Finney wrote:
> > I think that either of ‘Origin: vendor’ (for a patch created by the
> > package maintainer) or ‘Origin: other’ would be better than omitting the
> > field. I'd like to see the examples recommend
On Wed, Aug 26, 2009 at 01:56:35AM +0200, Raphael Hertzog wrote:
> I made some last changes to the DEP following round 4. You'll find them below.
> I plan to switch the DEP's status to CANDIDATE since it's about time to start
> using this new format to try it out. Once I've done this, I'll announce
On Wed, 26 Aug 2009, Ben Finney wrote:
> > In the sample above, if I wanted to add the Origin field I would do
> > something like this:
> > Origin: vendor: written by maintainer, see Author
>
> I think that either of ‘Origin: vendor’ (for a patch created by the
> package maintainer) or ‘Origin: ot
Raphael Hertzog writes:
> On Wed, 26 Aug 2009, Ben Finney wrote:
> > A minor point: If we're going to refer to the standard for these
> > fields, then RFC 2822 is obsoleted by the current draft standard,
> > RFC 5322 http://tools.ietf.org/html/rfc5322>.
>
> Shall we do this even if it's “only” a
On Wed, 26 Aug 2009, Ben Finney wrote:
> A minor point: If we're going to refer to the standard for these fields,
> then RFC 2822 is obsoleted by the current draft standard, RFC 5322
> http://tools.ietf.org/html/rfc5322>.
Shall we do this even if it's “only” a draft standard?
> > +A patch created
On Wed,26.Aug.09, 01:56:35, Raphael Hertzog wrote:
> +A patch created by the the Debian maintainer John Doe, which got
^^^
Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)
signature.asc
Description: Digital sig
Raphael Hertzog writes:
> I plan to switch the DEP's status to CANDIDATE since it's about time
> to start using this new format to try it out. Once I've done this,
> I'll announce it on d-d-a to encourage people to start using it.
Thanks for your ongoing work on this, I'm finding it useful.
> -
Hello,
I made some last changes to the DEP following round 4. You'll find them below.
I plan to switch the DEP's status to CANDIDATE since it's about time to start
using this new format to try it out. Once I've done this, I'll announce it on
d-d-a to encourage people to start using it.
Current ve
28 matches
Mail list logo
