All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Myers <bpm@sgi.com>
To: Zach Brown <zab@zabbo.net>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
	linux-ext4@vger.kernel.org, Rich Johnston <rjohnston@sgi.com>,
	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:52:40 -0500	[thread overview]
Message-ID: <20130327205240.GT22182@sgi.com> (raw)
In-Reply-To: <20130327204217.GC16651@lenny.home.zabbo.net>

Hey,

On Wed, Mar 27, 2013 at 01:42:17PM -0700, Zach Brown wrote:
> On Wed, Mar 27, 2013 at 03:05:12PM -0400, Theodore Ts'o wrote:
> > 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.)
> 
> It does seem like a good idea to help people map from descriptive names
> to their previous numeric file names.
> 
> But do we want to bake it in to the file names forevermore?  Would it be
> good enough to start the old tests with something like
> 
> _was_test_nr 45
> 
> that spits out the old test number in the log?
> 
> Just thinking out loud over here.

Maybe a text file containing the mapping would be sufficient.  It's not as if
it's going to grow.

-Ben

WARNING: multiple messages have this Message-ID (diff)
From: Ben Myers <bpm@sgi.com>
To: Zach Brown <zab@zabbo.net>
Cc: Rich Johnston <rjohnston@sgi.com>,
	linux-ext4@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>,
	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:52:40 -0500	[thread overview]
Message-ID: <20130327205240.GT22182@sgi.com> (raw)
In-Reply-To: <20130327204217.GC16651@lenny.home.zabbo.net>

Hey,

On Wed, Mar 27, 2013 at 01:42:17PM -0700, Zach Brown wrote:
> On Wed, Mar 27, 2013 at 03:05:12PM -0400, Theodore Ts'o wrote:
> > 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.)
> 
> It does seem like a good idea to help people map from descriptive names
> to their previous numeric file names.
> 
> But do we want to bake it in to the file names forevermore?  Would it be
> good enough to start the old tests with something like
> 
> _was_test_nr 45
> 
> that spits out the old test number in the log?
> 
> Just thinking out loud over here.

Maybe a text file containing the mapping would be sufficient.  It's not as if
it's going to grow.

-Ben

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

  reply	other threads:[~2013-03-27 20:52 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
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 [this message]
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=20130327205240.GT22182@sgi.com \
    --to=bpm@sgi.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=rjohnston@sgi.com \
    --cc=tytso@mit.edu \
    --cc=xfs@oss.sgi.com \
    --cc=zab@zabbo.net \
    /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.