From: Linus Torvalds <torvalds@linux-foundation.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Fix path-limited "rev-list --bisect" termination condition.
Date: Fri, 23 Mar 2007 15:39:36 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0703231538270.6730@woody.linux-foundation.org> (raw)
In-Reply-To: <7vps6zoal0.fsf@assigned-by-dhcp.cox.net>
On Fri, 23 Mar 2007, Junio C Hamano wrote:
>
> Is this the only issue you know about with respect to the
> BISECT_NAMES? You earlier said it was broken and suggested to
> remove it,...
That ending condition was the only one I knew about. If you have checked
that it works now, I say "keep it". At worst, it just points to the wrong
commit because people gave the wrong list of filenames, but hey, let's
burn that bridge when we get to it.
Linus
prev parent reply other threads:[~2007-03-23 22:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-23 21:57 [PATCH] Fix path-limited "rev-list --bisect" termination condition Junio C Hamano
2007-03-23 22:25 ` Linus Torvalds
2007-03-23 22:32 ` Junio C Hamano
2007-03-23 22:39 ` Linus Torvalds [this message]
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.0703231538270.6730@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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 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).