From: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>,
git@adamspiers.org, GIT Mailing-list <git@vger.kernel.org>,
felipe.contreras@gmail.com
Subject: Duplicate test numbers in pu.
Date: Wed, 21 Nov 2012 19:14:02 +0000 [thread overview]
Message-ID: <50AD27FA.3010006@ramsay1.demon.co.uk> (raw)
Hi Junio,
I noticed that the pu branch has two tests with number t0007, viz:
$ cd t
$ make test-lint-duplicates
duplicate test numbers: t0007
make: *** [test-lint-duplicates] Error 1
$
In particular, t/t0007-git-var.sh is added by branch 'jk/send-email-\
sender-prompt', while t/t0007-ignores.sh is added by branch 'as/check-ignore'.
Also:
$ make test-lint-executable
non-executable tests: t5801-remote-helpers.sh
make: *** [test-lint-executable] Error 1
$
(added in branch 'fc/fast-export-fixes').
HTH
ATB,
Ramsay Jones
next reply other threads:[~2012-11-21 19:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 19:14 Ramsay Jones [this message]
2012-11-22 10:35 ` Duplicate test numbers in pu Adam Spiers
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=50AD27FA.3010006@ramsay1.demon.co.uk \
--to=ramsay@ramsay1.demon.co.uk \
--cc=felipe.contreras@gmail.com \
--cc=git@adamspiers.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox