From: Andi Kleen <andi@firstfloor.org>
To: Ivan Bulatovic <combuster@gmx.com>
Cc: piotr@hosowicz.com, linux-kernel@vger.kernel.org
Subject: Re: What is 2.6.34-git1 and how to it it? And whether to eat it?
Date: Tue, 18 May 2010 22:06:39 +0200 [thread overview]
Message-ID: <87632lx9dc.fsf@basil.nowhere.org> (raw)
In-Reply-To: <1274196123.5720.158.camel@localhost.localdomain> (Ivan Bulatovic's message of "Tue\, 18 May 2010 17\:22\:03 +0200")
Ivan Bulatovic <combuster@gmx.com> writes:
> No, 2.6.34-git1 is set of patches that eventually will become 2.6.34.1
Actually I think it will become 2.6.35-rc1
The stable tree is elsewhere.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2010-05-18 20:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 15:11 What is 2.6.34-git1 and how to it it? And whether to eat it? Piotr Hosowicz
2010-05-18 15:22 ` Ivan Bulatovic
2010-05-18 15:32 ` Piotr Hosowicz
2010-05-18 19:56 ` Rafael J. Wysocki
2010-05-18 21:07 ` Ivan Bulatovic
2010-05-18 20:06 ` Andi Kleen [this message]
2010-05-18 16:01 ` Randy Dunlap
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=87632lx9dc.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=combuster@gmx.com \
--cc=linux-kernel@vger.kernel.org \
--cc=piotr@hosowicz.com \
/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;
as well as URLs for NNTP newsgroup(s).