linux-kernel - Re: - lis3lv02d-separate-the-core-from-hp-acpi-api.patch removed from -mm tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <1231794554.5405.6.camel@brick>
Date:	Mon, 12 Jan 2009 13:09:14 -0800
From:	Harvey Harrison <harvey.harrison@...il.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Pavel Machek <pavel@...e.cz>, eric.piel@...mplin-utc.net,
	linux-kernel@...r.kernel.org
Subject: Re: - lis3lv02d-separate-the-core-from-hp-acpi-api.patch removed
 from -mm tree

On Mon, 2009-01-12 at 12:49 -0800, Andrew Morton wrote:
> On Mon, 12 Jan 2009 21:30:44 +0100
> Pavel Machek <pavel@...e.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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/