public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com, aelder@sgi.com
Subject: Re: [GIT] fixes and cleanups for xfs-dev
Date: Fri, 4 Jun 2010 03:54:40 -0400	[thread overview]
Message-ID: <20100604075440.GA9325@infradead.org> (raw)
In-Reply-To: <20100604055837.GB20641@dastard>

On Fri, Jun 04, 2010 at 03:58:37PM +1000, Dave Chinner wrote:
> Hi Alex,
> 
> Here are the latest list of reviewed patches for the xfs-dev tree.
> The inode cluster freeing fix really needs to go to Linus for .35
> (and a .34-stable update is probably needed).

Yes, getting the current queue on oss plus the first fout patches
from your pull request into .35 ASAP would be a good thing.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2010-06-04  7:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-04  5:58 [GIT] fixes and cleanups for xfs-dev Dave Chinner
2010-06-04  7:54 ` Christoph Hellwig [this message]

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=20100604075440.GA9325@infradead.org \
    --to=hch@infradead.org \
    --cc=aelder@sgi.com \
    --cc=david@fromorbit.com \
    --cc=xfs@oss.sgi.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