From: "Nguyen Thai Ngoc Duy" <pclouds@gmail.com>
To: "Junio C Hamano" <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: Clueless bisect error message
Date: Wed, 11 Oct 2006 15:30:20 +0700 [thread overview]
Message-ID: <fcaeb9bf0610110130r42afc270l8e0b5db0b9861c05@mail.gmail.com> (raw)
In-Reply-To: <7v1wpfuv9d.fsf@assigned-by-dhcp.cox.net>
On 10/11/06, Junio C Hamano <junkio@cox.net> wrote:
> My point actually was that even a simple rewording is harder
> than it seems, because that cluelessness actually was introduced
> to help Cogito. If we do not care about it, we can just reword
> it to say "Hey you are in the middle of another bisect, or maybe
> you left your bisect by doing git-checkout earlier? In either
> case git-bisect --reset is your friend, oh, and we can run that
> for you now if you want". We could even remove head-name in
> git-checkout when we see one.
>
> But I suspect that doing either of these things would harm
> Cogito users. After cg-seek the user is not "in the middle of
> another bisect", and if we run "git bisect --reset" when we see
> head-name, it would probably break it too.
Thanks. Now I understand the issue. I'm sorry for my ignorant because
I haven't used cogito yet.
--
Duy
next prev parent reply other threads:[~2006-10-11 8:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 7:08 Clueless bisect error message Nguyen Thai Ngoc Duy
2006-10-11 7:22 ` Junio C Hamano
2006-10-11 7:50 ` Nguyen Thai Ngoc Duy
2006-10-11 8:11 ` Junio C Hamano
2006-10-11 8:30 ` Nguyen Thai Ngoc Duy [this message]
2006-10-11 9:14 ` Jeff King
2006-10-11 12:51 ` Krzysztof Halasa
2006-10-11 18:04 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fcaeb9bf0610110130r42afc270l8e0b5db0b9861c05@mail.gmail.com \
--to=pclouds@gmail.com \
--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).