From: Harvey Harrison <harvey.harrison@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Pavel Machek <pavel@suse.cz>,
eric.piel@tremplin-utc.net, linux-kernel@vger.kernel.org
Subject: Re: - lis3lv02d-separate-the-core-from-hp-acpi-api.patch removed from -mm tree
Date: Mon, 12 Jan 2009 13:09:14 -0800 [thread overview]
Message-ID: <1231794554.5405.6.camel@brick> (raw)
In-Reply-To: <20090112124947.79b7b74d.akpm@linux-foundation.org>
On Mon, 2009-01-12 at 12:49 -0800, Andrew Morton wrote:
> On Mon, 12 Jan 2009 21:30:44 +0100
> Pavel Machek <pavel@suse.cz> wrote:
>
> > BTW... "-" for both "patch is junk" and "patch is now mainline" is quite
> > confusing. Could we get you to use "-" for "patch was dropped because
> > it is junk" and "*" (or something) for "patch is now mainline"?
>
> I think I can manage that.
maybe:
-[short reason]patchname.patch
Examples
-[upstream]patchname.patch for mainline or subsytem tree
-[junk]patchname.patch
-[update]patchname.patch for 'updated version will be merged'
Or, if you started to track how things got upstream, then you could easily
let people know where to go looking for it.
-[mainline]
-[x86]
-[gregkh]
Just a thought.
Harvey
next prev parent reply other threads:[~2009-01-12 21:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200901121958.n0CJw9ke027350@imap1.linux-foundation.org>
2009-01-12 20:30 ` - lis3lv02d-separate-the-core-from-hp-acpi-api.patch removed from -mm tree Pavel Machek
2009-01-12 20:49 ` Andrew Morton
2009-01-12 21:09 ` Harvey Harrison [this message]
[not found] <200901091958.n09JwbJs031498@imap1.linux-foundation.org>
2009-01-09 23:00 ` Pavel Machek
2009-01-09 23:23 ` Andrew Morton
2009-01-09 23:37 ` Éric Piel
2009-01-09 23:55 ` Andrew Morton
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=1231794554.5405.6.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=eric.piel@tremplin-utc.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox