From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/3] iproute2: upgrade to 3.4.0
Date: Tue, 17 Jul 2012 14:41:51 +0100 [thread overview]
Message-ID: <1997389.yhY4ZDbdgv@helios> (raw)
In-Reply-To: <19F41A1C-D530-4725-AB58-4193025996BB@dominion.thruhere.net>
On Tuesday 17 July 2012 15:27:01 Koen Kooi wrote:
> Op 17 jul. 2012, om 15:08 heeft Paul Eggleton het volgende geschreven:
> > On Tuesday 17 July 2012 12:24:41 Andrei Gherzan wrote:
> >> On Tue, Jul 17, 2012 at 11:28 AM, Cristian Iorga
> >>
> >> <cristian.iorga@intel.com>wrote:
> >>> +PR = "r0"
> >>
> >> Not needed anymore. (The same mention for wpa-s. and pulseaudio.)
> >
> > This is not a hard-and-fast rule for OE-Core AFAIK.
>
> It would be *very* nice to get rid of all PR = r0 instances in the complete
> oe metaverse.
I haven't yet heard a compelling argument as to why it's such a great idea to
keep removing it. For my part, leaving PR = "r0" just means the PR line stays
in the same place instead of jumping around when people remove and add it in
different locations within the recipe.
Of course, once we move to using the PR server this is a moot point.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-07-17 13:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 8:28 [PATCH 1/3] iproute2: upgrade to 3.4.0 Cristian Iorga
2012-07-17 8:28 ` [PATCH 2/3] pulseaudio: upgrade to 2.0 Cristian Iorga
2012-07-17 18:53 ` Saul Wold
2012-07-18 12:40 ` Iorga, Cristian
2012-07-17 8:28 ` [PATCH 3/3] wpa-supplicant: upgrade to 1.0 Cristian Iorga
2012-07-17 19:01 ` Saul Wold
2012-07-18 12:09 ` Iorga, Cristian
2012-07-17 9:24 ` [PATCH 1/3] iproute2: upgrade to 3.4.0 Andrei Gherzan
2012-07-17 13:08 ` Paul Eggleton
2012-07-17 13:27 ` Koen Kooi
2012-07-17 13:41 ` Paul Eggleton [this message]
2012-07-17 13:29 ` Andrei Gherzan
2012-07-17 18:58 ` Saul Wold
2012-07-18 11:50 ` Iorga, Cristian
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=1997389.yhY4ZDbdgv@helios \
--to=paul.eggleton@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@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.