From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: git@vger.kernel.org
Subject: [BUG] git branch --merged $unknown_checksum segfaults
Date: Mon, 27 Feb 2012 13:26:09 +0100 [thread overview]
Message-ID: <20120227122609.GA26981@mx.loc> (raw)
Hi,
I hope this minor buglet is not known already..
I did not look further.
Seen with
$ dpkg-query -W git
git 1:1.7.2.5-3
and
git 1:1.7.9-1
cheers,
git init
git branch --merged 0000000000000000000000000000000000000000
Segmentation fault
touch f
git commit -m one f
[master (root-commit) f11ad60] one
0 files changed, 0 insertions(+), 0 deletions(-)
create mode 100644 f
git branch --merged $((echo "obase=16;ibase=16;$(git log -n1 --format='%H'| tr '[[:lower:]]' '[[:upper:]]')+1") | bc)
Segmentation fault
next reply other threads:[~2012-02-27 12:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 12:26 Bernhard Reutner-Fischer [this message]
2012-02-27 15:11 ` [PATCH] branch: don't assume the merge filter ref exists Carlos Martín Nieto
2012-02-27 18:05 ` Junio C Hamano
2012-02-27 19:30 ` Jeff King
2012-02-27 19:33 ` Junio C Hamano
2012-02-27 19:43 ` Jeff King
2012-02-28 15:14 ` Carlos Martín Nieto
2012-02-28 17:32 ` Junio C Hamano
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=20120227122609.GA26981@mx.loc \
--to=rep.dot.nop@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).