Re: [RFC] new -stable tag variant, Git workflow question

[Ingo Molnar]

* James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx> wrote:

> On Tue, 2009-11-10 at 05:20 +0100, Ingo Molnar wrote:
> > * Greg KH <gregkh@xxxxxxx> 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?

Let me re-quote what you quoted above:

> > > > I've attached the full commit below. [...]

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