From: "Stefan Pfetzing" <stefan.pfetzing@gmail.com>
To: "Git Mailing List" <git@vger.kernel.org>
Subject: t8001-annotate.sh fails on Mac OS X
Date: Fri, 26 May 2006 01:53:58 +0200 [thread overview]
Message-ID: <f3d7535d0605251653m15db34f3j46403f4ed0c4c69f@mail.gmail.com> (raw)
Hi,
for some reason I could not yet figure out, t8001-annotate.sh fails at test 18.
--- snip ---
* ok 17: some edit
* expecting success: check_count A 1 B 1 B1 1 B2 1 "A U Thor" 1 C 1 D 1
Author A (expected 1, attributed 1) good
Author B1 (expected 1, attributed 1) good
Author D (expected 1, attributed 2) bad
Author A U Thor (expected 1, attributed 1) good
Author B2 (expected 1, attributed 1) good
Author B (expected 1, attributed 1) good
* FAIL 18: some edit
check_count A 1 B 1 B1 1 B2 1 "A U Thor" 1 C 1 D 1
* failed 1 among 18 test(s)
--- snap ---
And git-annotate in the trash dir produces the following:
--- snip ---
5c085656 ( A 2006-05-25 23:13:26 +0000 1)lazy dog
3f3e26a3 ( B2 2006-05-25 23:13:29 +0000 2)4A
quick brown lazy dog fox jumps over the
3b509ebb ( B 2006-05-25 23:13:27 +0000 3)lazy dog
669d4e82 ( D 2006-05-25 23:13:35 +0000 4)99
slow green fox jumps into the
f96b8861 ( B1 2006-05-25 23:13:28 +0000 5)well.
a7bad43f ( A U Thor 2006-05-25 23:13:31 +0000 6)evil merge.
669d4e82 ( D 2006-05-25 23:13:35 +0000 7)incomplete
--- snap ---
The strange point is, git log is completely ok:
--- snip ---
commit 90ef4f653d6dc33d90ce826303563e5506d5ad31
Author: C <author@example.com>
Date: Thu May 25 23:13:34 2006 +0000
Incomplete
--- snap ---
bye
Stefan
--
http://www.dreamind.de/
Oroborus and Debian GNU/Linux Developer.
next reply other threads:[~2006-05-25 23:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 23:53 Stefan Pfetzing [this message]
2006-05-26 1:11 ` t8001-annotate.sh fails on Mac OS X Shawn Pearce
2006-05-26 3:02 ` Junio C Hamano
2006-05-26 3:12 ` Martin Langhoff
2006-05-27 1:40 ` Ryan Anderson
2006-05-26 4:32 ` Fredrik Kuivinen
2006-05-26 13:36 ` Johannes Schindelin
2006-05-26 13:51 ` Stefan Pfetzing
2006-05-27 18:13 ` Nicolas Vilz 'niv'
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=f3d7535d0605251653m15db34f3j46403f4ed0c4c69f@mail.gmail.com \
--to=stefan.pfetzing@gmail.com \
--cc=git@vger.kernel.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).