From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] GFS2 git tree
Date: Mon, 21 Jan 2008 10:17:52 +0000 [thread overview]
Message-ID: <1200910672.22038.165.camel@quoit> (raw)
Hi,
I've just rebased the tree due to the impending merge window. Also I've
removed all of the DLM patches since there will shortly be a separate
DLM tree. I'm going to hold off accepting any larger patches now until
after the merge window,
Steve.
next reply other threads:[~2008-01-21 10:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 10:17 Steven Whitehouse [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-02-03 10:00 [Cluster-devel] GFS2 git tree Steven Whitehouse
2013-02-22 10:01 Steven Whitehouse
2012-12-17 10:55 Steven Whitehouse
2012-05-22 10:28 Steven Whitehouse
2011-01-21 10:18 Steven Whitehouse
2010-03-29 14:37 Steven Whitehouse
2009-12-07 9:08 Steven Whitehouse
2009-07-31 10:14 Steven Whitehouse
2009-03-24 11:36 Steven Whitehouse
2008-11-10 14:51 Steven Whitehouse
2008-01-28 13:02 Steven Whitehouse
2007-05-14 7:21 Steven Whitehouse
2007-04-26 10:25 [Cluster-devel] GFS2 Git tree 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=1200910672.22038.165.camel@quoit \
--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).