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] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 13 Mar 2009 11:08:07 +0100
From:	Thomas Renninger <trenn@...e.de>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Andreas Herrmann <andreas.herrmann3@....com>,
	Ingo Molnar <mingo@...hat.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org,
	Yinghai Lu <yinghai@...nel.org>,
	"Greg Kroah-Hartman" <gregkh@...ell.com>
Subject: How to submit patches that should be considered for stable inclusion also [Was: Re: [PATCH v2] x86: mtrr: ...]

On Friday 13 March 2009 10:18:12 Ingo Molnar wrote:
> 
> * Thomas Renninger <trenn@...e.de> wrote:
> 
> > What does -stable backport tag mean?
> 
> It means such lines added to commit logs:
> 
>     Cc: <stable@...nel.org>
Thanks. That was the bit I liked to know.
> 
> Pointing out specific examples where the backport was realized 
> when the fix was committed but the tag was not added or outright 
> lost, and talking to those those maintainers might help. Often 
> it's a matter of "Oh, cool, did not know that!" realization.
Yep. Same for me.
> 
> Interestingly, the second-ever such tag i found in Git history 
> was for a fix ... from you:
I did this more intuitively.
If this is how it should be done, this info should be spread
to maintainers and repeated some times until really everybody
is looking at it. This is not much work. The backporting itself
might be, but this could be done by the author or distributions looking out 
for that tag. At least much less important "easy" fixes shouldn't slip 
through or take a long time until someone realizes that they are missing.

Thanks,

     Thomas
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ