From: Junio C Hamano <gitster@pobox.com>
To: Torstein Hegge <hegge@resisty.net>
Cc: Christian Couder <chriscool@tuxfamily.org>, git@vger.kernel.org
Subject: Re: [PATCH] bisect: Store first bad commit as comment in log file
Date: Mon, 22 Apr 2013 14:13:00 -0700 [thread overview]
Message-ID: <7vr4i2nuar.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20130422210229.GE5650@pvv.ntnu.no> (Torstein Hegge's message of "Mon, 22 Apr 2013 23:02:29 +0200")
Torstein Hegge <hegge@resisty.net> writes:
> I took another look at this. I wasn't able to come up with anything
> useful for the "The merge base $rev is bad" case, but for the "only
> skipped commits left to test" case one could do something like this.
We skipped them because we can gain _no_ information from testing
these commits. They are not even "possibly bad", but are "unknown".
So it feels to me that by definition listing them would not be
useful. What am I missing?
next prev parent reply other threads:[~2013-04-22 21:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-13 15:22 [PATCH] bisect: Store first bad commit as comment in log file Torstein Hegge
2013-04-15 4:38 ` Christian Couder
2013-04-15 9:53 ` Torstein Hegge
2013-04-15 15:00 ` Junio C Hamano
2013-04-22 21:02 ` Torstein Hegge
2013-04-22 21:13 ` Junio C Hamano [this message]
2013-04-22 22:20 ` Torstein Hegge
2013-04-22 22:37 ` Junio C Hamano
2013-04-25 4:26 ` Christian Couder
2013-05-22 22:27 ` [PATCH] bisect: Fix log output for multi-parent skip ranges Torstein Hegge
2013-04-15 6:50 ` [PATCH] bisect: Store first bad commit as comment in log file 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=7vr4i2nuar.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=hegge@resisty.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.