From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] GFS2: Tracing pre-pull patch posting
Date: Fri, 12 Jun 2009 13:52:35 +0100 [thread overview]
Message-ID: <1244811157-7558-1-git-send-email-swhiteho@redhat.com> (raw)
Hi,
As promised, these are the patches for the second GFS2 merge in this
merge window. The interesting patch is the tracing one, now that all
the prerequisites have been merge. The other one is a minor update
due to a recently merged VFS patch,
Steve.
next reply other threads:[~2009-06-12 12:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 12:52 Steven Whitehouse [this message]
2009-06-12 12:52 ` [Cluster-devel] [PATCH 1/2] GFS2: Add tracepoints Steven Whitehouse
2009-06-12 12:52 ` [Cluster-devel] [PATCH 2/2] GFS2: Remove lock_kernel from gfs2_put_super() 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=1244811157-7558-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