From: Nicolas Pitre <nico@cam.org>
To: git@vger.kernel.org
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: builtin git-shortlog still broken
Date: Fri, 08 Dec 2006 22:23:14 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0612082205240.2630@xanadu.home> (raw)
On the Linux kernel repository, doing "git shortlog v2.6.18.." works
fine. "git shortlog v2.6.17.." works fine. "git shortlog v2.6.16.." also
works fine. But "git shortlog v2.6.15.." dies with a segmentation
fault. Trying "git log v2.6.15.. | git shortlog" also produces the same
crash while "git log v2.6.16.. | git shortlog" works fine.
The old perl version doesn't have any such issue with those test cases,
not even with the whole kernel history.
next reply other threads:[~2006-12-09 3:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-09 3:23 Nicolas Pitre [this message]
2006-12-09 4:04 ` [PATCH] shortlog: fix segfault on empty authorname Jeff King
2006-12-09 21:56 ` Nicolas Pitre
2006-12-09 23:21 ` Johannes Schindelin
2006-12-10 3:45 ` Jeff King
2006-12-10 6:01 ` Junio C Hamano
2006-12-10 22:43 ` Johannes Schindelin
2006-12-09 23:34 ` builtin git-shortlog still broken Johannes Schindelin
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=Pine.LNX.4.64.0612082205240.2630@xanadu.home \
--to=nico@cam.org \
--cc=Johannes.Schindelin@gmx.de \
--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).