From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: Remove xfs_check for 3.2.0?
Date: Fri, 9 May 2014 06:39:37 +1000 [thread overview]
Message-ID: <20140508203936.GV5421@dastard> (raw)
In-Reply-To: <536BCF95.201@sandeen.net>
On Thu, May 08, 2014 at 01:40:21PM -0500, Eric Sandeen wrote:
> I think we had stated removal in June 2014, but it seems close enough.
>
> Should xfs_check be removed prior to 3.2.0's release?
I'd prefer to do it slightly later than earlier.
As it is, 3.2.0 is really in the "critical fixes only" stage - like
that repair prefetch bug. So apart from fixes like that, I don't
want to be changing things right now.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-05-08 20:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 18:40 Remove xfs_check for 3.2.0? Eric Sandeen
2014-05-08 20:39 ` Dave Chinner [this message]
2014-05-08 20:40 ` Eric Sandeen
2014-05-08 21:04 ` Emmanuel Florac
2014-05-08 22:02 ` 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=20140508203936.GV5421@dastard \
--to=david@fromorbit.com \
--cc=sandeen@sandeen.net \
--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