From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] GFS2: Pre-pull patch posting
Date: Mon, 1 Mar 2010 15:08:21 +0000 [thread overview]
Message-ID: <1267456106-3084-1-git-send-email-swhiteho@redhat.com> (raw)
Hi,
Not so many patches for GFS2 this merge window. The bulk of the changes are
aimed at reducing overheads when caching large numbers of inodes and
the consequent simplification of the umount code,
Steve.
next reply other threads:[~2010-03-01 15:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 15:08 Steven Whitehouse [this message]
2010-03-01 15:08 ` [Cluster-devel] [PATCH 1/5] GFS2: Metadata address space clean up Steven Whitehouse
2010-03-01 15:08 ` [Cluster-devel] [PATCH 2/5] GFS2: Remove loopy umount code Steven Whitehouse
2010-03-01 15:08 ` [Cluster-devel] [PATCH 3/5] GFS2: Remove old, unused linked list code from quota Steven Whitehouse
2010-03-01 15:08 ` [Cluster-devel] [PATCH 4/5] GFS2: ordered writes are backwards Steven Whitehouse
2010-03-01 15:08 ` [Cluster-devel] [PATCH 5/5] GFS2: print glock numbers in hex Steven Whitehouse
-- strict thread matches above, loose matches on Subject: below --
2015-02-10 10:36 [Cluster-devel] GFS2: Pre-pull patch posting Steven Whitehouse
2013-04-05 9:57 Steven Whitehouse
2013-01-03 11:50 Steven Whitehouse
2010-10-18 14:15 Steven Whitehouse
2010-08-02 9:27 Steven Whitehouse
2010-05-17 12:40 Steven Whitehouse
2010-03-11 17:21 Steven Whitehouse
2009-09-10 11:27 Steven Whitehouse
2009-06-10 8:30 Steven Whitehouse
2009-03-18 12:23 [Cluster-devel] [GFS2] " swhiteho
2008-12-17 11:29 [Cluster-devel] GFS2: " swhiteho
2008-09-26 12:00 Steven Whitehouse
2008-07-11 10:11 [Cluster-devel] [GFS2] " swhiteho
2008-04-17 8:37 swhiteho
2008-01-21 9:21 swhiteho
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=1267456106-3084-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).