From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] powertop: update to 2.0+git
Date: Mon, 16 Jul 2012 11:36:47 +0100 [thread overview]
Message-ID: <5766114.d2laZrfaXp@helios> (raw)
In-Reply-To: <8F9AE1A6-06B6-432B-B336-B8F72D3C2697@dominion.thruhere.net>
On Monday 16 July 2012 12:33:00 Koen Kooi wrote:
> Op 16 jul. 2012, om 10:47 heeft Burton, Ross het volgende geschreven:
> > On 16 July 2012 07:11, Koen Kooi <koen@dominion.thruhere.net> wrote:
> >>> Please add proper Upstream-Status for the patches; it is nice to have
> >>> those to track the pending patches.
> >>
> >> Isn't that field only used to put in "pending" and then backslap each
> >> other on doing such a good job?>
> > Personally I find it incredibly useful to differentiate between
> > patches that should be going upstream and patches that are OE-specific
> > for various reasons.
>
> I'm not debating the usefulness of the U-S field, I'm debating the
> usefulness of using 'Pending' as a catch-all. I can do:
>
> for patch in *.patch ; do
> echo "Upstream-Status: Pending" >> $patch
> done
>
> And it will get accepted, but is ultimately useless.
No, it is not. It signifies that the patch is considered appropriate by the
submitter for upstreaming.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-07-16 10:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-14 9:59 [PATCH] powertop: update to 2.0+git Koen Kooi
2012-07-14 11:46 ` Koen Kooi
2012-07-15 21:25 ` Otavio Salvador
2012-07-16 6:11 ` Koen Kooi
2012-07-16 8:47 ` Burton, Ross
2012-07-16 10:33 ` Koen Kooi
2012-07-16 10:36 ` Paul Eggleton [this message]
2012-07-16 11:25 ` Koen Kooi
2012-07-16 12:07 ` Richard Purdie
2012-07-16 10:37 ` Burton, Ross
2012-07-16 10:44 ` Phil Blundell
2012-07-16 10:48 ` Burton, Ross
2012-07-16 9:59 ` Richard Purdie
2012-07-16 12:28 ` Otavio Salvador
2012-07-16 13:22 ` Koen Kooi
2012-07-16 13:34 ` Otavio Salvador
2012-07-16 13:40 ` Koen Kooi
2012-07-16 15:23 ` Otavio Salvador
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=5766114.d2laZrfaXp@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.