From: Ben Myers <bpm@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: userspace releases?
Date: Wed, 26 Sep 2012 16:42:14 -0500 [thread overview]
Message-ID: <20120926214214.GF13214@sgi.com> (raw)
In-Reply-To: <20120926091554.GA13559@infradead.org>
Hey,
On Wed, Sep 26, 2012 at 05:15:54AM -0400, Christoph Hellwig wrote:
> On Tue, Sep 25, 2012 at 02:43:55PM -0500, Ben Myers wrote:
> > Hey Christoph,
> >
> > On Tue, Sep 25, 2012 at 05:50:02AM -0400, Christoph Hellwig wrote:
> > > It's been 6 month since the last releases, and we've acquired a fair
> > > amount of fixes in xfsprogs. I think it's time to put out another
> > > release soon.
> >
> > Seems like a good idea to me. How would you prefer to define 'soon'?
>
> Given the expected rush with the 3.7 merge window I'm perfectly fine
> doing it just after that, say mid-October.
Mid-October sounds good!
-Ben
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-09-26 21:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 9:50 userspace releases? Christoph Hellwig
2012-09-25 19:43 ` Ben Myers
2012-09-26 9:15 ` Christoph Hellwig
2012-09-26 21:42 ` Ben Myers [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=20120926214214.GF13214@sgi.com \
--to=bpm@sgi.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