From: Jeff King <peff@peff.net>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Johannes Sixt <j6t@kdbg.org>
Subject: Re: [PATCH/RFC] t800?-blame.sh: retitle uniquely
Date: Mon, 13 Dec 2010 12:07:34 -0500 [thread overview]
Message-ID: <20101213170734.GA24736@sigill.intra.peff.net> (raw)
In-Reply-To: <52f777e518583955f78b71e96b3c8ff53d25b608.1292256498.git.git@drmicha.warpmail.net>
On Mon, Dec 13, 2010 at 05:12:29PM +0100, Michael J Gruber wrote:
> On a related note to J6t's patch, how's the stance on unique titles?
> Unique numbers are important for partial test runs, of course,
> but unique titles help finding you way through the test.
> There are more than the blame.sh ones.
I don't think it is a big deal, but I did just 5 minutes ago get annoyed
at:
t7500-commit.sh
t7501-commit.sh
t7502-commit.sh
t7509-commit.sh
Speaking of minor test issues, we should probably also do this:
-- >8 --
Subject: [PATCH] tests: flip executable bit on t9158
All tests are supposed to be executable.
Signed-off-by: Jeff King <peff@peff.net>
---
0 files changed, 0 insertions(+), 0 deletions(-)
mode change 100644 => 100755 t/t9158-git-svn-mergeinfo.sh
diff --git a/t/t9158-git-svn-mergeinfo.sh b/t/t9158-git-svn-mergeinfo.sh
old mode 100644
new mode 100755
--
1.7.3.3.784.gccc31.dirty
next prev parent reply other threads:[~2010-12-13 17:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 10:14 [PATCH] Avoid duplicate test number t7609 Johannes Sixt
2010-12-13 16:12 ` [PATCH/RFC] t800?-blame.sh: retitle uniquely Michael J Gruber
2010-12-13 17:07 ` Jeff King [this message]
2010-12-13 17:22 ` Jeff King
2010-12-13 19:38 ` Junio C Hamano
2010-12-13 19:51 ` Junio C Hamano
2010-12-13 19:58 ` Jeff King
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=20101213170734.GA24736@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
/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).