DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=to:cc:subject
	:references:from:date:message-id:mime-version:content-type; q=
	dns; s=sasl; b=td0FFh5inNMxlvmp/QWtOvok2Y64xIrYahNi6TFH1W+3RfvQ9
	n5qHYvvIiP9pPLtz/802LaYFLKF0PCXvHUdaMFotUf6aWAV7Do92xcfZmL6RNnqW
	3wbsJIMfE9KQY/PHy1fBfSk6lo3IcT2sI09XA3Vp1/ut0z8URTdKrrYqZ8=
To: Ingo Molnar <mingo@elte.hu>
Cc: Greg KH <gregkh@suse.de>, Stefan Richter <stefanr@s5r6.in-berlin.de>,
       James Bottomley <James.Bottomley@HansenPartnership.com>,
       Linus Torvalds <torvalds@linux-foundation.org>,
       Andrew Morton <akpm@linux-foundation.org>,
       Chris Wright <chrisw@sous-sol.org>, linux-kernel@vger.kernel.org,
       Thomas Gleixner <tglx@linutronix.de>, "H. Peter Anvin" <hpa@zytor.com>,
       Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [RFC] new -stable tag variant, Git workflow question
References: <20091110034831.GB26809@elte.hu> <20091110041452.GA25575@suse.de>
 <1257863388.4184.220.camel@mulgrave.site>
 <4AF98C36.9040405@s5r6.in-berlin.de> <20091110193919.GC12686@suse.de>
 <20091110204537.GB18509@elte.hu>
From: Junio C Hamano <gitster@pobox.com>
Date: Tue, 10 Nov 2009 13:11:17 -0800
Message-ID: <7vhbt23x1m.fsf@alter.siamese.dyndns.org>
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1051
Lines: 22

Ingo Molnar <mingo@elte.hu> writes:

> Yeah. This new tagging scheme doesnt really allow anything 'new' per se 
> - it just helps the existing practice some more. All these commits were 
> -stable candidates anyway, in exactly the same order - the only 
> difference the new tagging scheme adds here is a more organized, 
> in-upsream-Git way of communicating it to you.

I am just a bystander, but if it were truly in-upstream-git way, wouldn't
you be forking a branch from the tagged target release (the latest of
2.6.32.X), and queuing only the changes meant for -stable to it, and
giving the name of the branch to git people and sending out patches from
that branch for e-mailed review and application?

There won't be any special tagging required, only a dedicated branch.

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