From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 5/5] gfs2: dlm based recovery coordination
Date: Thu, 5 Jan 2012 11:16:06 -0500 [thread overview]
Message-ID: <20120105161606.GB22610@redhat.com> (raw)
In-Reply-To: <1325778009.2690.42.camel@menhir>
On Thu, Jan 05, 2012 at 03:40:09PM +0000, Steven Whitehouse wrote:
> I think it would be a good plan to not send this last patch for the
> current merge window and let it settle for a bit longer. Running things
> so fine with the timing makes me nervous bearing in mind the number of
> changes,
To allay your fears, keep in mind that the big new feature here does not
impact the current mode in the slightest. Everything should continue to
work just as it has before given the current versions of dlm_controld and
gfs_controld. So, there should be no reason for worry. A version of
dlm_controld under development will enable the new feature.
> and that three issues have been caught in the last few days.
The issues that arose from -next were completely inconsequential in
practice, so that's a moot point.
> Lets try and resolve the remaining points and then we can have something
> really solid ready for the next window.
I don't know of any remaining points.
> I don't think there is any particular rush to get it in at the moment.
I think people will want to start using the new cluster4 components (which
require these patches) before a 3.4 kernel would be in a Fedora release.
So the motivation is to avoid making everyone build their own kernels and
allow cluster4 versions of things to be put in Fedora.
Dave
next prev parent reply other threads:[~2012-01-05 16:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-16 22:03 [Cluster-devel] [PATCH 5/5] gfs2: dlm based recovery coordination David Teigland
2011-12-19 13:07 ` Steven Whitehouse
2011-12-19 17:47 ` David Teigland
2011-12-20 10:39 ` Steven Whitehouse
2011-12-20 19:16 ` David Teigland
2011-12-20 21:04 ` David Teigland
2011-12-21 10:45 ` Steven Whitehouse
2011-12-21 15:40 ` David Teigland
2011-12-22 21:23 ` David Teigland
2011-12-23 9:19 ` Steven Whitehouse
2011-12-19 15:17 ` Steven Whitehouse
2012-01-05 15:08 ` Bob Peterson
2012-01-05 15:21 ` David Teigland
2012-01-05 15:40 ` Steven Whitehouse
2012-01-05 16:16 ` David Teigland [this message]
2012-01-05 16:45 ` Bob Peterson
-- strict thread matches above, loose matches on Subject: below --
2012-01-05 16:46 David Teigland
2012-01-05 16:58 ` Steven Whitehouse
2012-01-05 17:13 ` David Teigland
2012-01-09 16:36 ` Steven Whitehouse
2012-01-09 16:46 ` David Teigland
2012-01-09 17:00 ` David Teigland
2012-01-09 17:04 ` Steven Whitehouse
2012-01-09 17:02 ` 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=20120105161606.GB22610@redhat.com \
--to=teigland@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).