public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: preparing a new xfsprogs release?
Date: Thu, 25 Aug 2011 16:19:59 +1000	[thread overview]
Message-ID: <20110825061959.GN3162@dastard> (raw)
In-Reply-To: <20110825050828.GA30775@infradead.org>

On Thu, Aug 25, 2011 at 01:08:28AM -0400, Christoph Hellwig wrote:
> We have the libxfs resync and a healthy amount of fixes in xfsprogs,
> what about cutting a release in about 1-2 weeks from now?

Probably a good idea.

Once it is release, I'll look at doing another kernel code sync -
this one will be a lot smaller than the last - and then we can start
adding all the new stuff we've got on top of it...

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

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

  reply	other threads:[~2011-08-25  6:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-25  5:08 preparing a new xfsprogs release? Christoph Hellwig
2011-08-25  6:19 ` Dave Chinner [this message]
2011-08-25  6:23   ` Christoph Hellwig
2011-08-25  7:09     ` Dave Chinner

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=20110825061959.GN3162@dastard \
    --to=david@fromorbit.com \
    --cc=hch@infradead.org \
    --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