From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] GFS2: Git tree update
Date: Mon, 28 Sep 2009 09:42:32 +0100 [thread overview]
Message-ID: <1254127352.6052.368.camel@localhost.localdomain> (raw)
Hi,
Since -rc1 is now out, I've rebased the -nmw git tree to that. Also I've
temporarily dropped out the patch removing the sysfs files as there
appears to still be some userspace issues there. I'll resubmit that
patch once those issues are dealt with.
I've also pushed in the patch for making the subsequent meta mounts work
correctly. Its a slightly different version to the last one, since the
bd_mount_sem has gone away, but is otherwise identical,
Steve.
next reply other threads:[~2009-09-28 8:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-28 8:42 Steven Whitehouse [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-29 8:29 [Cluster-devel] [GFS2] Git tree update Steven Whitehouse
2007-10-29 10:25 ` Fabio Massimo Di Nitto
2007-10-31 15:34 ` Steven Whitehouse
2007-11-01 7:30 ` Fabio Massimo Di Nitto
2007-11-08 17:35 ` Fabio Massimo Di Nitto
2007-11-12 11:48 ` Fabio Massimo Di Nitto
2007-09-25 8:55 [Cluster-devel] GFS2 git " Steven Whitehouse
2007-08-06 7:37 Steven Whitehouse
2007-04-06 9:19 [Cluster-devel] [GFS2] Git " 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=1254127352.6052.368.camel@localhost.localdomain \
--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 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).