From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] GFS2: Pre-pull patch posting (merge window set #2)
Date: Wed, 11 Jan 2012 12:57:23 +0000 [thread overview]
Message-ID: <1326286648-5515-1-git-send-email-swhiteho@redhat.com> (raw)
Hi,
The following patch set contains one large patch which was previously
in the DLM tree (and hence also in linux-next) but which is entirely
focused on GFS2, and has thus been moved into the GFS2 tree after
the merge of the recent DLM patches. In addition there are a few small
bug fixes too,
Steve.
next reply other threads:[~2012-01-11 12:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 12:57 Steven Whitehouse [this message]
2012-01-11 12:57 ` [Cluster-devel] [PATCH 1/5] GFS2: dlm based recovery coordination Steven Whitehouse
2012-01-11 12:57 ` [Cluster-devel] [PATCH 2/5] GFS2: Fix a use-after-free that coverity spotted Steven Whitehouse
2012-01-11 12:57 ` [Cluster-devel] [PATCH 3/5] GFS2: let spectator mount do read only recovery Steven Whitehouse
2012-01-11 12:57 ` [Cluster-devel] [PATCH 4/5] GFS2: fail mount if journal recovery fails Steven Whitehouse
2012-01-11 12:57 ` [Cluster-devel] [PATCH 5/5] GFS2: Fix nlink setting on inode creation 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=1326286648-5515-1-git-send-email-swhiteho@redhat.com \
--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).