All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Rich Johnston <rjohnston@sgi.com>
Cc: xfs-oss <xfs@oss.sgi.com>,
	linux-ext4@vger.kernel.org,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Announce re-factor all current xfstests patches request
Date: Wed, 27 Mar 2013 15:05:12 -0400	[thread overview]
Message-ID: <20130327190512.GA22889@thunk.org> (raw)
In-Reply-To: <5153217B.5070909@sgi.com>

What do you think about renaming the existing tests from NNN to
NNN-descriptive-name?  That way it will be easier for people who are
trying to track regressions, since they can easily map from the new
more descriptive name to the old test number for comparison purposes
(i.e., to see whether a failure is a regression or not, etc.)

Would you be open to changes which did this?  I'd suggest sending the
changes as a shell script to minimize the chances of patch conflicts.
It will cause people to need to regenerate their patches, but that
means now would be the time to do this, when everyone will need to be
fixing up their outstanding changes anyway.  :-)

       	      	      		- Ted

WARNING: multiple messages have this Message-ID (diff)
From: Theodore Ts'o <tytso@mit.edu>
To: Rich Johnston <rjohnston@sgi.com>
Cc: linux-ext4@vger.kernel.org,
	linux-btrfs <linux-btrfs@vger.kernel.org>,
	xfs-oss <xfs@oss.sgi.com>
Subject: Re: Announce re-factor all current xfstests patches request
Date: Wed, 27 Mar 2013 15:05:12 -0400	[thread overview]
Message-ID: <20130327190512.GA22889@thunk.org> (raw)
In-Reply-To: <5153217B.5070909@sgi.com>

What do you think about renaming the existing tests from NNN to
NNN-descriptive-name?  That way it will be easier for people who are
trying to track regressions, since they can easily map from the new
more descriptive name to the old test number for comparison purposes
(i.e., to see whether a failure is a regression or not, etc.)

Would you be open to changes which did this?  I'd suggest sending the
changes as a shell script to minimize the chances of patch conflicts.
It will cause people to need to regenerate their patches, but that
means now would be the time to do this, when everyone will need to be
fixing up their outstanding changes anyway.  :-)

       	      	      		- Ted

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

  reply	other threads:[~2013-03-27 19:05 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-27 13:23 Announce re-factor all current xfstests patches request Rich Johnston
2013-03-27 13:23 ` Rich Johnston
2013-03-27 13:46 ` Theodore Ts'o
2013-03-27 13:46   ` Theodore Ts'o
2013-03-27 16:42   ` Rich Johnston
2013-03-27 16:42     ` Rich Johnston
2013-03-27 19:05     ` Theodore Ts'o [this message]
2013-03-27 19:05       ` Theodore Ts'o
2013-03-27 20:42       ` Zach Brown
2013-03-27 20:42         ` Zach Brown
2013-03-27 20:52         ` Ben Myers
2013-03-27 20:52           ` Ben Myers
2013-03-28  0:34         ` Dave Chinner
2013-03-28  0:34           ` Dave Chinner
2013-03-27 21:02       ` Dave Chinner
2013-03-27 21:02         ` Dave Chinner
2013-03-27 20:54   ` Dave Chinner
2013-03-27 20:54     ` Dave Chinner
2013-03-27 21:48     ` Theodore Ts'o
2013-03-27 21:48       ` Theodore Ts'o
2013-03-28  0:35       ` Dave Chinner
2013-03-28  0:35         ` 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=20130327190512.GA22889@thunk.org \
    --to=tytso@mit.edu \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=rjohnston@sgi.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 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.