From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] GFS2 -nmw tree
Date: Tue, 17 Sep 2013 11:44:13 +0100 [thread overview]
Message-ID: <1379414653.2722.15.camel@menhir> (raw)
Hi,
Now that the merge window is done, I've rebased the tree to -rc1 as per
usual. There are four patches in there at the moment, with more likely
to land very shortly. So after a quieter time recently, there are lots
of developments which are likely to be ready in the next short period,
Steve.
next reply other threads:[~2013-09-17 10:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 10:44 Steven Whitehouse [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-01-03 10:21 [Cluster-devel] GFS2 -nmw tree Steven Whitehouse
2013-04-09 14:10 Steven Whitehouse
2012-07-26 10:24 Steven Whitehouse
2011-05-10 12:47 Steven Whitehouse
2010-11-30 10:57 Steven Whitehouse
2009-11-05 14:12 Steven Whitehouse
2006-12-08 11:34 Steven Whitehouse
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=1379414653.2722.15.camel@menhir \
--to=swhiteho@redhat.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.