All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Carl Worth <cworth@cworth.org>
Cc: Mike Galbraith <efault@gmx.de>, git <git@vger.kernel.org>
Subject: Re: [PATCH] Eliminate confusing "won't bisect on seeked tree" failure
Date: Fri, 22 Feb 2008 09:18:03 -0800	[thread overview]
Message-ID: <7v63wgap10.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 87pruqfc59.wl%cworth@cworth.org

Carl Worth <cworth@cworth.org> writes:

> This error message is very confusing---it doesn't tell the user
> anything about how to fix the situation. And the actual fix
> for the situation ("git bisect reset") does a checkout of a
> potentially random branch, (compared to what the user wants to
> be on for the bisect she is starting).

The message itself refers to a Cogito "feature" and I suspect
that removing the check and refusal would confuse Cogito.  While
I think the patch itself is Ok for us, we may want to wait a bit
for a while. until Cogito users all die out.

  reply	other threads:[~2008-02-22 17:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-21  5:20 bisect: "won't bisect on seeked tree" Mike Galbraith
2008-02-21  5:33 ` Shawn O. Pearce
2008-02-21  5:39   ` Mike Galbraith
2008-02-21  5:43     ` Shawn O. Pearce
2008-02-21  6:00       ` Mike Galbraith
2008-02-21 17:32 ` [PATCH] Eliminate confusing "won't bisect on seeked tree" failure Carl Worth
2008-02-22 17:18   ` Junio C Hamano [this message]
2008-02-23  9:21     ` Karl Hasselström
2008-02-23 18:33     ` Carl Worth
2008-02-23 22:59       ` Junio C Hamano
2008-02-24  1:14         ` Carl Worth

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=7v63wgap10.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=cworth@cworth.org \
    --cc=efault@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 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.