From: "Øyvind A. Holm" <sunny@sunbase.org>
To: Git mailing list <git@vger.kernel.org>
Cc: Michael Haggerty <mhagger@alum.mit.edu>
Subject: [BUG] b9c8e7f2fb6e breaks git bisect visualize
Date: Wed, 14 Jun 2017 02:06:32 +0200 [thread overview]
Message-ID: <20170614000630.44uctc5y7dyyleqy@sunbase.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 535 bytes --]
Commit b9c8e7f2fb6e ("prefix_ref_iterator: don't trim too much") breaks
git bisect visualize, this reproduces the bug:
$ git bisect start
$ git bisect bad
$ git bisect good HEAD^^
$ git bisect visualize
fatal: BUG: attempt to trim too many characters
$
Reverting b9c8e7f2fb6e makes git bisect visualize work again.
Tested on Debian GNU/Linux 8.8 (jessie).
Øyvind
N 60.37604° E 5.33339°
OpenPGP fingerprint: A006 05D6 E676 B319 55E2 E77E FB0C BEE8 94A5 06E5
dcacbb24-5094-11e7-b7e4-db5caa6d21d3
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next reply other threads:[~2017-06-14 0:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 0:06 Øyvind A. Holm [this message]
2017-06-14 8:36 ` [BUG] b9c8e7f2fb6e breaks git bisect visualize Michael Haggerty
2017-06-14 9:07 ` [PATCH 0/2] Fix a refname trimming problem in `log --bisect` Michael Haggerty
2017-06-14 9:07 ` [PATCH 1/2] for_each_bisect_ref(): don't trim refnames Michael Haggerty
2017-06-14 9:22 ` Jeff King
2017-06-14 9:32 ` Jeff King
2017-06-14 10:05 ` Junio C Hamano
2017-06-15 22:26 ` Junio C Hamano
2017-06-14 9:07 ` [PATCH 2/2] prefix_ref_iterator_advance(): relax the check of trim length Michael Haggerty
2017-06-14 9:24 ` [PATCH 0/2] Fix a refname trimming problem in `log --bisect` Jeff King
2017-06-14 10:09 ` Junio C Hamano
2017-06-14 9:18 ` [BUG] b9c8e7f2fb6e breaks git bisect visualize 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170614000630.44uctc5y7dyyleqy@sunbase.org \
--to=sunny@sunbase.org \
--cc=git@vger.kernel.org \
--cc=mhagger@alum.mit.edu \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).