From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Nguyen Thai Ngoc Duy <pclouds@gmail.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Jakub Narebski <jnareb@gmail.com>,
git@vger.kernel.org
Subject: Re: cloning a tree which has detached branch checked out
Date: Tue, 07 Feb 2012 09:11:00 -0800 [thread overview]
Message-ID: <7v4nv236xn.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20120207153225.GA14773@sigill.intra.peff.net> (Jeff King's message of "Tue, 7 Feb 2012 10:32:25 -0500")
Jeff King <peff@peff.net> writes:
> On Tue, Feb 07, 2012 at 07:57:08PM +0700, Nguyen Thai Ngoc Duy wrote:
>
>> On Tue, Feb 7, 2012 at 5:41 PM, Michael S. Tsirkin <mst@redhat.com> wrote:
>> >> > #git clone -n lab:/home/mst/scm/linux
>> >> > ....
>> >> > error: Trying to write ref HEAD with nonexistant object
>> >> > cec64082f689f949a397cb9b39423dc41545fa0e
>> >> > fatal: Cannot update the ref 'HEAD'.
>> >> >
>> >> > Looks like a bug, doesn't it?
>> >> ...
>
> This particular bug should have been fixed before that, even, with my
> c1921c1 (clone: always fetch remote HEAD, 2011-06-07). And it is tested
> explicitly in t5707,...
That was my thought when I first saw it. The failure case was that HEAD
was pointing at something no ref reaches, and clone was only grabbing the
tips of branches, which failed to transfer the history leading to HEAD.
> ... So I think your guess about a subtle error in the local ref
> processing is a reasonable one.
What is funny is "error: Trying to write ref HEAD with nonexistant object".
"git grep -e nonexistant f3fb0" does not register any hit.
Could it be that mysterious "lab:" protocol handler that is misbehaving?
next prev parent reply other threads:[~2012-02-07 17:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 7:06 cloning a tree which has detached branch checked out Michael S. Tsirkin
2012-02-07 10:08 ` Jakub Narebski
2012-02-07 10:41 ` Michael S. Tsirkin
2012-02-07 12:57 ` Nguyen Thai Ngoc Duy
2012-02-07 13:02 ` Michael S. Tsirkin
2012-02-07 13:07 ` Nguyen Thai Ngoc Duy
2012-02-07 15:32 ` Jeff King
2012-02-07 17:11 ` Junio C Hamano [this message]
2012-02-07 17:16 ` Jeff King
2012-02-08 10:17 ` Michael S. Tsirkin
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=7v4nv236xn.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=mst@redhat.com \
--cc=pclouds@gmail.com \
--cc=peff@peff.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.