From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] GFS2: Pull request (fixes)
Date: Fri, 5 Apr 2013 12:27:47 -0400 [thread overview]
Message-ID: <20130405162746.GD20835@redhat.com> (raw)
In-Reply-To: <1365158085.2735.25.camel@menhir>
On Fri, Apr 05, 2013 at 11:34:45AM +0100, Steven Whitehouse wrote:
> Please consider pulling the following changes,
There's some mixup here that should be cleared up first.
> David Teigland (2):
> GFS2: Fix unlock of fcntl locks during withdrawn state
>
> Steven Whitehouse (1):
> GFS2: Fix unlock of fcntl locks during withdrawn state
WARNING: multiple messages have this Message-ID (diff)
From: David Teigland <teigland@redhat.com>
To: Steven Whitehouse <swhiteho@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, cluster-devel@redhat.com
Subject: Re: GFS2: Pull request (fixes)
Date: Fri, 5 Apr 2013 12:27:47 -0400 [thread overview]
Message-ID: <20130405162746.GD20835@redhat.com> (raw)
In-Reply-To: <1365158085.2735.25.camel@menhir>
On Fri, Apr 05, 2013 at 11:34:45AM +0100, Steven Whitehouse wrote:
> Please consider pulling the following changes,
There's some mixup here that should be cleared up first.
> David Teigland (2):
> GFS2: Fix unlock of fcntl locks during withdrawn state
>
> Steven Whitehouse (1):
> GFS2: Fix unlock of fcntl locks during withdrawn state
next prev parent reply other threads:[~2013-04-05 16:27 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 10:34 [Cluster-devel] GFS2: Pull request (fixes) Steven Whitehouse
2013-04-05 10:34 ` Steven Whitehouse
2013-04-05 16:27 ` David Teigland [this message]
2013-04-05 16:27 ` David Teigland
2013-04-05 16:51 ` [Cluster-devel] " Steven Whitehouse
2013-04-05 16:51 ` Steven Whitehouse
2013-04-05 16:53 ` [Cluster-devel] " Linus Torvalds
2013-04-05 16:53 ` Linus Torvalds
2013-04-05 17:52 ` [Cluster-devel] " Steven Whitehouse
2013-04-05 17:52 ` Steven Whitehouse
-- strict thread matches above, loose matches on Subject: below --
2014-09-16 10:11 [Cluster-devel] " Steven Whitehouse
2014-07-18 11:21 Steven Whitehouse
2014-01-02 12:41 Steven Whitehouse
2013-11-22 10:39 Steven Whitehouse
2013-08-19 9:26 Steven Whitehouse
2013-08-19 16:33 ` Linus Torvalds
2013-08-19 9:24 Steven Whitehouse
2013-06-04 15:40 Steven Whitehouse
2013-05-24 14:05 Steven Whitehouse
2013-01-28 10:31 Steven Whitehouse
2013-01-03 12:28 Steven Whitehouse
2012-11-07 10:58 Steven Whitehouse
2012-09-13 13:42 Steven Whitehouse
2012-04-11 10:21 Steven Whitehouse
2012-04-11 10:18 Steven Whitehouse
2012-02-28 11:49 Steven Whitehouse
2011-07-27 10:00 Steven Whitehouse
2011-07-14 15:16 Steven Whitehouse
2011-05-23 14:05 Steven Whitehouse
2011-04-19 9:13 Steven Whitehouse
2011-01-19 10:50 Steven Whitehouse
2010-11-29 13:42 Steven Whitehouse
2010-11-15 15:41 Steven Whitehouse
2010-09-17 13:59 Steven Whitehouse
2010-07-15 14:35 Steven Whitehouse
2010-05-25 8:51 Steven Whitehouse
2010-03-11 17:41 Steven Whitehouse
2010-02-12 11:37 Steven Whitehouse
2010-02-04 10:06 Steven Whitehouse
2010-02-02 10:07 [Cluster-devel] [GFS2] " Steven Whitehouse
2010-01-11 14:24 [Cluster-devel] GFS2: " Steven Whitehouse
2009-08-14 13:01 Steven Whitehouse
2009-07-30 13:45 [Cluster-devel] GFS2: Pre-pull patch posting (fixes) Steven Whitehouse
2009-07-30 13:02 ` [Cluster-devel] GFS2: Pull request (fixes) Steven Whitehouse
2009-04-23 13:13 Steven Whitehouse
2009-01-07 10:21 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=20130405162746.GD20835@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 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.