From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] GFS2 git tree rebase
Date: Wed, 10 Oct 2007 13:09:45 +0100 [thread overview]
Message-ID: <1192018185.1068.382.camel@quoit> (raw)
Hi,
Linus has released 2.6.23, so I've rebased against that. I'm not now,
expecting to put any more patches into the -nmw tree until after the
merge window, so that any patches that I've been sent recently and which
haven't made it into the current tree will go into the next -nmw tree
unless they turn out to be particularly urgent,
Steve.
next reply other threads:[~2007-10-10 12:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 12:09 Steven Whitehouse [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-23 9:38 [Cluster-devel] GFS2 git tree rebase Steven Whitehouse
2007-06-05 12:46 [Cluster-devel] [GFS2] Git " Steven Whitehouse
2007-05-11 10:49 Steven Whitehouse
2007-03-16 10:33 [Cluster-devel] GFS2 git " Steven Whitehouse
2007-01-18 16:22 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=1192018185.1068.382.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 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.