From: Jakub Narebski <jnareb@gmail.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: git@vger.kernel.org
Subject: Re: cloning a tree which has detached branch checked out
Date: Tue, 07 Feb 2012 02:08:33 -0800 (PST) [thread overview]
Message-ID: <m362fjklb7.fsf@localhost.localdomain> (raw)
In-Reply-To: <20120207070628.GA24698@redhat.com>
"Michael S. Tsirkin" <mst@redhat.com> writes:
> I have a tree where I checked out a remote, without
> creating a local branch, this detaches the HEAD:
> # git branch
> * (no branch)
> master
> #git log|head -1
> commit cec64082f689f949a397cb9b39423dc41545fa0e
> #git log master..HEAD|head -1
> commit cec64082f689f949a397cb9b39423dc41545fa0e
>
>
> Now if I try to clone it:
> #git clone -n lab:/home/mst/scm/linux
> Initialized empty Git repository in /home/mst/scm/linux/.git/
> remote: Counting objects: 1693446, done.
> remote: Compressing objects: 100% (277054/277054), done.
> Receiving objects: 100% (1693446/1693446), 418.16 MiB | 7.63 MiB/s,
> done.
> remote: Total 1693446 (delta 1414353), reused 1681280 (delta 1402358)
> Resolving deltas: 100% (1414353/1414353), done.
> error: Trying to write ref HEAD with nonexistant object
> cec64082f689f949a397cb9b39423dc41545fa0e
> fatal: Cannot update the ref 'HEAD'.
>
> Looks like a bug, doesn't it?
Which git version? IIRC there was some bugfix recently in that
area...
--
Jakub Narebski
next prev parent reply other threads:[~2012-02-07 10:08 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 [this message]
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
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=m362fjklb7.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=mst@redhat.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;
as well as URLs for NNTP newsgroup(s).