All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] GFS2 git trees
Date: Tue, 18 Jan 2011 17:27:21 +0000	[thread overview]
Message-ID: <1295371641.2533.68.camel@dolmen> (raw)

Hi,

Just a heads up on what is happening....

In the -fixes tree there are currently a couple of patches which I'm
intending to merge shortly.

The -nmw tree is currently empty, but there are two pending patches (one
is the RCU glock patch and the other is the update post-RCU path
walking) which I'll put in just as soon as the current merge window
closes.

Steve.




             reply	other threads:[~2011-01-18 17:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-18 17:27 Steven Whitehouse [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-07-21  9:55 [Cluster-devel] GFS2 git trees Steven Whitehouse
2013-01-29 10:58 Steven Whitehouse
2013-01-04 11:03 Steven Whitehouse
2013-01-02 11:17 [Cluster-devel] GFS2: Git trees Steven Whitehouse
2012-04-24 16:14 [Cluster-devel] GFS2 git trees Steven Whitehouse
2012-04-12 10:45 Steven Whitehouse
2012-03-22 10:36 Steven Whitehouse
2012-02-28 17:42 [Cluster-devel] GFS2: " Steven Whitehouse
2012-01-16 10:13 [Cluster-devel] GFS2 " Steven Whitehouse
2011-10-31  9:31 Steven Whitehouse
2011-10-27  8:16 Steven Whitehouse
     [not found] ` <20111028022502.be20e4714658f8de02ec6a18@canb.auug.org.au>
2011-10-27 15:41   ` Steven Whitehouse
2011-10-24 12:20 Steven Whitehouse
2011-10-21 12:49 Steven Whitehouse
2011-10-17  9:37 Steven Whitehouse
2011-03-17 10:58 Steven Whitehouse
2010-02-02 21:33 Steven Whitehouse
2010-01-12  9:30 Steven Whitehouse
2009-04-27  8:42 Steven Whitehouse
2009-04-07 15:21 Steven Whitehouse
2007-03-08  9:37 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=1295371641.2533.68.camel@dolmen \
    --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.