From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] GFS2/DLM git tree
Date: Wed, 17 Oct 2007 14:47:01 +0100 [thread overview]
Message-ID: <1192628821.1068.437.camel@quoit> (raw)
Hi,
So as you've probably all noticed by now, Linus has merged the previous
-nmw git tree earlier this week and I've thus started a new one.
Although I rebased it last night, I'm about to do it again when I push
that last set of patches that I just posted. Thats because I managed to
pull from Linus at a time when kbuild was broken for x86 (and which I
spent some of this morning trying to work out why I was getting a zImage
when I'd asked for a bzImage!).
If you've sent me a patch recently and its not in the tree, and wasn't
merged in this merge window, then I've lost/fogrotten it, so please
check to see that I have everything I ought to have. I don't think I've
lost anything, but now is a good time to check and let me know.
Although there have been a lot of patches recently, I'm expecting the
rate of change to be somewhat slower over the next few weeks at least,
Steve.
next reply other threads:[~2007-10-17 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 13:47 Steven Whitehouse [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-18 12:40 [Cluster-devel] GFS2/DLM git tree Steven Whitehouse
2007-05-08 9:26 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=1192628821.1068.437.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).