Git development
 help / color / mirror / Atom feed
From: Alexandre Julliard <julliard@winehq.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: [PATCH] checkout: Don't crash when switching away from an invalid branch.
Date: Sat, 08 Nov 2008 11:07:25 +0100	[thread overview]
Message-ID: <87k5bea5uq.fsf@wine.dyndns.org> (raw)
In-Reply-To: <7vbpwrf85x.fsf@gitster.siamese.dyndns.org> (Junio C. Hamano's message of "Fri, 07 Nov 2008 15:06:18 -0800")

Junio C Hamano <gitster@pobox.com> writes:

> For that matter, dying without removing the trace of that funny state
> might be even preferrable if you need to do postmortem to figure out why
> you got into such a funny state to begin with, but not everybody uses git
> to debug git.

It turns out to be user error, that was a tree I hadn't used in a long
time and I didn't realize it was using alternates, so HEAD was pointing
to a commit that had been rebased and garbage-collected in the source
repository.

Most other commands die with a "bad object HEAD" in that situation, and
checkout could certainly do that too, but I think it's nicer to provide
an easy way of getting out of that broken state.  I'll resend an updated
patch.

-- 
Alexandre Julliard
julliard@winehq.org

  reply	other threads:[~2008-11-08 10:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-07 17:02 [PATCH] checkout: Don't crash when switching away from an invalid branch Alexandre Julliard
2008-11-07 18:05 ` Johannes Schindelin
2008-11-07 22:28   ` Alexandre Julliard
2008-11-07 23:06     ` Junio C Hamano
2008-11-08 10:07       ` Alexandre Julliard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-11-08 12:03 Alexandre Julliard

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=87k5bea5uq.fsf@wine.dyndns.org \
    --to=julliard@winehq.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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