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 13:42:38 -0500 [thread overview]
Message-ID: <4AFB059E.50801@balister.org> (raw)
In-Reply-To: <20091111174317.GB11484@jama>
On 11/11/2009 12:43 PM, Martin Jansa wrote:
> On Wed, Nov 11, 2009 at 10:45:11AM -0500, Denys Dmytriyenko wrote:
>> On Wed, Nov 11, 2009 at 04:27:08PM +0100, Martin Jansa wrote:
>>> * Holger Hans Peter Freyther<zecke@openmoko.org> did for the OM git
>>> tree that was never merged back into OE.
>>> * Taken from xora/angstrom-srcpv branch where it rot for long enough
>>
>> We also discussed it during the OEDEM...
>
> RP said you did on #oe
> 16:25:45< RP> JaMa|Wrk: I can't sanction that, needs to be proposed on
> list but I'd ack it
> 16:26:18< XorA> JaMa|Wrk: got my Ack
> 16:26:46< RP> It was mentioned informally at OEDEM and nobody I talked
> to objected...
>
> Mickey acked too on #openmoko-cdevel
> 16:47:28< JaMa|Wrk> mickey|office: ack for SRCPV?
> 16:50:47< mickey|office> ya
>
> So that's at least 3 ACKs, if there is no objection today I'll push it.
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.
Philip
next prev parent reply other threads:[~2009-11-11 18:44 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 [this message]
2009-11-11 21:15 ` Richard Purdie
2009-11-11 21:49 ` Phil Blundell
2009-11-11 22:57 ` Philip Balister
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=4AFB059E.50801@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.