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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 10 Nov 2009 09:30:32 -0500
From:	James Bottomley <>
To:	Ingo Molnar <>
Cc:	Greg KH <>,
	Linus Torvalds <>,
	Andrew Morton <>,
	Chris Wright <>,, Thomas Gleixner <>,
	"H. Peter Anvin" <>,
	Peter Zijlstra <>
Subject: Re: [RFC] new -stable tag variant, Git workflow question

On Tue, 2009-11-10 at 05:20 +0100, Ingo Molnar wrote:
> * Greg KH <> wrote:
> > > I've attached the full commit below. The prereq commits are not 
> > > uptream yet, and they dont carry a -stable backporting tag as the 
> > > -stable relevance was not anticipated at that point yet. They will 
> > > all be upstream in the next merge window when Linus merges the 
> > > relevant tree - and then all these tags become visible to the 
> > > -stable team's scripts.
> > > 
> > > What do you think about this new -stable tagging variant? To me it 
> > > looks quite intuitive, less error-prone and it is more informative 
> > > as well. Furthermore, it gives us some freedom to mark commits as 
> > > backport candidates later on. I kept them oneliners for the purpose 
> > > of making them all self-sufficient tags.
> > 
> > I agree.
> Ok - thanks for the confirmation - i've pushed out the first such 
> commit. (Let me know if there's any problem with it down the line - it 
> will be a few weeks, in the next merge window, until it truly 
> 'activates' for -stable.)

Can you give me the commit id in your tree so I can run a few tests?



To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists