From: Greg Kroah-Hartman <gregkh@suse.de>
To: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, stable@kernel.org
Subject: Future of Linux 2.6.22.y series
Date: Mon, 5 Nov 2007 10:13:32 -0800 [thread overview]
Message-ID: <20071105181332.GB28628@kroah.com> (raw)
For the last release, I stated that I thought the 2.6.22.12 release
would be the last one in the 2.6.22.y series. Since then, I've received
a number of other patches that would be nice to have in the .22.y tree.
So, for a while, I'll keep the 2.6.22.y tree open, doing new releases
every once in a while as they accumulate. I do this, for no other than
the selfish reason that I use it every day on my openSuSE 10.3 boxes as
that is the kernel base that release is on :)
If anyone has any objections or questions about this, please let me
know.
thanks,
greg k-h
next reply other threads:[~2007-11-05 18:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 18:13 Greg Kroah-Hartman [this message]
2007-11-06 11:26 ` Future of Linux 2.6.22.y series Jan Kara
2007-11-06 11:38 ` Christian Borntraeger
2007-11-06 20:00 ` Willy Tarreau
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=20071105181332.GB28628@kroah.com \
--to=gregkh@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--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