cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2] Git tree status
Date: Wed, 25 Jun 2008 09:53:56 +0100	[thread overview]
Message-ID: <1214384036.3481.15.camel@localhost.localdomain> (raw)

Hi,

I've just been catching up after getting back from holiday. Yesterday I
sent to minor bug fixes to Linus, so today I've just updated the -nmw
git tree by rebasing to Linus' latest kernel.

There are a few patches which I have left in my queue to look at and
possibly include in the upcoming merge window, and I'll try to get to
those shortly.

If you've been following the progress of GFS2 closely, then you'll see
that there are far fewer patches for this merge window than there have
been on previous occasions. This is a result of the slower rate of
change as things stabilise, and I hope that we'll be able to keep future
merges as small. It is of course helped by the fact that the DLM now has
its own tree as well.

The current patch naming convention of [subsys] <patch description>
which was taken from the network patch naming scheme is not used by
other parts of the kernel. They use subsys: <patch description> instead.
The network tree has changed to this new scheme and its my plan to do
the same for the GFS2 tree _after_ this next merge window. Until then
I'll continue to use the current system, so this is just a heads up on
that change.

As usual, if there are any questions/comments, drop me a line,

Steve.




                 reply	other threads:[~2008-06-25  8:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1214384036.3481.15.camel@localhost.localdomain \
    --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).