From: "Chris Friesen" <cfriesen@nortel.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
Greg KH <gregkh@suse.de>, Ingo Molnar <mingo@elte.hu>,
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
Date: Tue, 10 Nov 2009 13:12:42 -0600 [thread overview]
Message-ID: <4AF9BB2A.7060109@nortel.com> (raw)
In-Reply-To: <4AF98C36.9040405@s5r6.in-berlin.de>
On 11/10/2009 09:52 AM, Stefan Richter wrote:
> More importantly, isn't this against the character of the -stable kernel
> branches as _safe and simple_ hotfix branches?
>
> If a fix has a number of prerequisites which ar not -stable fixes
> themselves, then it is more than a hint that this fix is not really well
> suited for -stable.
Alternately, it's conceivable that the prerequisites were not
in-and-of-themselves candidates for -stable (maybe they didn't do
anything by themselves) but when combined with the final commit the
overall change is suitable for inclusion in -stable.
Chris
next prev parent reply other threads:[~2009-11-10 19:15 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 3:48 [RFC] new -stable tag variant, Git workflow question Ingo Molnar
2009-11-10 4:14 ` Greg KH
2009-11-10 4:20 ` Ingo Molnar
2009-11-10 14:30 ` James Bottomley
2009-11-10 17:22 ` Ingo Molnar
2009-11-10 17:53 ` Linus Torvalds
2009-11-10 18:06 ` Ingo Molnar
2009-11-10 14:29 ` James Bottomley
2009-11-10 15:52 ` Stefan Richter
2009-11-10 19:12 ` Chris Friesen [this message]
2009-11-10 21:20 ` Ingo Molnar
2009-11-10 19:39 ` Greg KH
2009-11-10 20:45 ` Ingo Molnar
2009-11-10 21:11 ` Junio C Hamano
2009-11-10 21:25 ` Greg KH
2009-11-10 21:29 ` Ingo Molnar
2009-11-10 19:37 ` Greg KH
2009-11-10 20:39 ` Ingo Molnar
2009-11-11 18:50 ` James Bottomley
2009-11-11 20:00 ` Linus Torvalds
2009-11-11 20:06 ` James Bottomley
2009-11-11 20:14 ` Linus Torvalds
2009-11-11 21:43 ` H. Peter Anvin
2009-11-11 21:52 ` Linus Torvalds
2009-11-12 7:45 ` Ingo Molnar
2009-11-12 15:15 ` H. Peter Anvin
2009-11-12 17:01 ` David Dillow
2009-11-12 19:50 ` H. Peter Anvin
2009-11-12 14:41 ` James Bottomley
2009-11-12 4:41 ` Greg KH
2009-11-12 16:11 ` James Bottomley
2009-11-19 18:15 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AF9BB2A.7060109@nortel.com \
--to=cfriesen@nortel.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=chrisw@sous-sol.org \
--cc=gregkh@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=stefanr@s5r6.in-berlin.de \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox