From: Fabio M. Di Nitto <fabbione@ubuntu.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] tarball release matching 2.6.24
Date: Sat, 26 Jan 2008 19:25:21 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0801261922510.6826@trider-g7> (raw)
In-Reply-To: <479B19DF.5030800@wol.de>
On Sat, 26 Jan 2008, Marc - A. Dahlhaus wrote:
> Hello list,
>
> gfs-kernel in HEAD is out of sync with 2.6.24.
Yes we are aware of this. Most of the patches have been posted a while ago
on the mailing list and we were waiting for final .24 to be out.
> Is there a plan to push out an updated tarbal release matching 2.6.24 soon?
The patches should hit CVS HEAD this week.. i can't talk for a release as
I can't do them.
> Is there already a STABLE2 branch in any location?
Not yet. I know they are working on it at RedHat. There are a few things
that need to happen in a certain sequence for this branch to be available.
> thanks in advance,
welcome :)
Fabio
--
I'm going to make him an offer he can't refuse.
prev parent reply other threads:[~2008-01-26 18:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-26 11:30 [Cluster-devel] tarball release matching 2.6.24 Marc - A. Dahlhaus
2008-01-26 18:25 ` Fabio M. Di Nitto [this message]
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=Pine.LNX.4.64.0801261922510.6826@trider-g7 \
--to=fabbione@ubuntu.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).