From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] bitbake.conf: SRCPV always upgradeable paths for git recipes
Date: Wed, 11 Nov 2009 17:57:39 -0500 [thread overview]
Message-ID: <4AFB4163.9080208@balister.org> (raw)
In-Reply-To: <1257976192.25369.434.camel@lenovo.internal.reciva.com>
On 11/11/2009 04:49 PM, Phil Blundell wrote:
> On Wed, 2009-11-11 at 13:42 -0500, Philip Balister wrote:
>> Can people please get in the habit of using proper acks for patches?
>> This fishing though the random forms people are using is getting tiresome.
>>
>> For me: Acked-by: Philip Balister<philip@balister.org>
>>
>> Patchwork will pick these up, so it makes tracking things much easier.
>> Even if you agree to ack something in irc, please follow up with the
>> proper ack on the mailing list.
>
> What exactly does patchwork do with them? From a casual browse of
> http://patchwork.openembedded.org/patch/1256/ it doesn't seem as if that
> line in your email has produced any different effect to the other
> replies in this thread.
>
>> From your comment about tracking being much easier, it seems like there
> must be something else going on that I am not spotting. Maybe you could
> post a quick "idiot's guide to patchwork" or some such.
Real quick, click on the download mbox and you should see Grame's
signed-off-by and Richard's Acked-by added to the patch. When you apply
this to git, it will retain those lines.
I made mine not quit fit the format since I hadn't reviewed the patch.
The other reason is to use standard notation so people do not have to
collect ack statements in various forms, from various sources. We should
use the standard forms, not something we invent internally.
Philip
>
> p.
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
prev parent reply other threads:[~2009-11-11 22:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 15:27 [PATCH] bitbake.conf: SRCPV always upgradeable paths for git recipes Martin Jansa
2009-11-11 15:37 ` Graeme Gregory
2009-11-12 9:10 ` Martin Jansa
2009-11-11 15:45 ` Denys Dmytriyenko
2009-11-11 17:43 ` Martin Jansa
2009-11-11 18:42 ` Philip Balister
2009-11-11 21:15 ` Richard Purdie
2009-11-11 21:49 ` Phil Blundell
2009-11-11 22:57 ` Philip Balister [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AFB4163.9080208@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.