All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
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 21:56:44 +0200	[thread overview]
Message-ID: <201005182156.44518.rjw@sisk.pl> (raw)
In-Reply-To: <1274196123.5720.158.camel@localhost.localdomain>

On Tuesday 18 May 2010, Ivan Bulatovic wrote:
> No, 2.6.34-git1 is set of patches that eventually will become 2.6.34.1

Not quite.

2.6.34-git1 contains changes that will appear in 2.6.35 (if they are not
reverted in the meantime), but not necessarily in 2.6.34.1.

The only changes from 2.6.34-git1 that will go into 2.6.34.1 are important bug
fixes.

Thanks,
Rafael

  parent reply	other threads:[~2010-05-18 19:55 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 [this message]
2010-05-18 21:07     ` Ivan Bulatovic
2010-05-18 20:06   ` Andi Kleen
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=201005182156.44518.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.