From: Wendy Cheng <wcheng@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [RHEL5 PATCH] GFS2: Fix gfs2_rename deadlock
Date: Mon, 08 Jan 2007 14:19:34 -0500 [thread overview]
Message-ID: <45A29946.8070308@redhat.com> (raw)
In-Reply-To: <1168266071.11844.23.camel@quoit.chygwyn.com>
Steven Whitehouse wrote:
>
> Can you send a version of this vs. upstream so that I can then get it in
> the -git tree? I think the changes vs. what is already in the -git tree
> are actually quite small,
>
Sorry to hold you up ... this is the version rebased to "nmw" tree
pulled this morning... Wendy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gfs2_meta_nlink.patch
Type: text/x-patch
Size: 5039 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20070108/7f0c83d1/attachment.bin>
prev parent reply other threads:[~2007-01-08 19:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-06 5:05 [Cluster-devel] [RHEL5 PATCH] GFS2: Fix gfs2_rename deadlock Wendy Cheng
2007-01-08 14:21 ` Steven Whitehouse
2007-01-08 19:19 ` Wendy Cheng [this message]
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=45A29946.8070308@redhat.com \
--to=wcheng@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).