From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] git trees
Date: Fri, 08 Jan 2010 14:49:09 +0000 [thread overview]
Message-ID: <1262962149.2764.20.camel@localhost> (raw)
Hi,
After some delay due to a couple of tricky issues, I'm now back updating
the GFS2 git trees again. I will probably send a pull request for the
fixes tree fairly shortly now, I'm just giving it a day or two in -next
first.
At the moment -fixes and -nmw are identical, but I will start pushing
more patches into -nmw shortly too,
Steve.
reply other threads:[~2010-01-08 14:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1262962149.2764.20.camel@localhost \
--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.