From: Junio C Hamano <junkio@cox.net>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Test names
Date: Tue, 05 Sep 2006 01:28:13 -0700 [thread overview]
Message-ID: <7vd5aaiuoy.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <edifa7$h29$1@sea.gmane.org> (Jakub Narebski's message of "Tue, 05 Sep 2006 02:10:59 +0200")
Jakub Narebski <jnareb@gmail.com> writes:
> In t/README it is written:
>...
> Is there any naming rule, or just increment it by one when adding new test
> in the same family?
>
>> Third digit (optionally) tells the particular switch or group of switches
>> we are testing.
>
> What tells the fourth digit?
Nothing other than just to make them aline up and ordered
nicely.
The rule was outlined long time ago but not strictly followed
(primarily because was done when git was mostly core, and it did
not anticipate the proliferation of Porcelain-ish wrappers, so
it was rather hard to follow). I'd suggest you to declare that
t92xx- series are for gitweb, and organize the tests in that
namespace nicely. Also you might want to see what Eric did for
the subversion interface tests (60d02cc declares that t91xx-
series are SVN tests and gives an easy way to skip heavier tests
on git-svn).
prev parent reply other threads:[~2006-09-05 8:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-05 0:10 Test names Jakub Narebski
2006-09-05 8:28 ` Junio C Hamano [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=7vd5aaiuoy.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.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;
as well as URLs for NNTP newsgroup(s).