From: Ivan Bulatovic <combuster@gmx.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
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 23:07:12 +0200 [thread overview]
Message-ID: <1274216832.2206.106.camel@localhost.localdomain> (raw)
In-Reply-To: <201005182156.44518.rjw@sisk.pl>
Thanks Rafael for clearing that up, Piotr - sorry for the mixup, I was
100% certain that 2.6.34-git1 were patches for the stable tree. I have
to read the docs more carefully instead of jumping to conclusions :)
I've just checked, there were no patches in the stable tree since the
release of 2.6.34 but there are some merges in the mainline. Got it
now :)
On Tue, 2010-05-18 at 21:56 +0200, Rafael J. Wysocki wrote:
> 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
> --
> 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/
next prev parent reply other threads:[~2010-05-18 21:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 15:11 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 [this message]
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=1274216832.2206.106.camel@localhost.localdomain \
--to=combuster@gmx.com \
--cc=linux-kernel@vger.kernel.org \
--cc=piotr@hosowicz.com \
--cc=rjw@sisk.pl \
/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
all inboxes | Powered by JetHome®