All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Jakub Narebski <jnareb@gmail.com>, git@vger.kernel.org
Subject: Re: cloning a tree which has detached branch checked out
Date: Tue, 7 Feb 2012 19:57:08 +0700	[thread overview]
Message-ID: <CACsJy8DtmQLX+Lfng-QRzVg9sfo8gQMXB-xTtPYpt+R2gModTg@mail.gmail.com> (raw)
In-Reply-To: <20120207104100.GA24828@redhat.com>

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?
>>
>> Which git version?  IIRC there was some bugfix recently in that
>> area...
>
> Sorry, forgot to mention that. It's pretty recent:
> $ git --version
> git version 1.7.9.111.gf3fb0

The series that Jakub mentioned is probably nd/clone-detached 5ce2b97,
which is already included in your tree. Does 1.7.9 work?

I tried but it was ok for me. I think ref processing at local probably
goes wrong and does not request commit from HEAD.  If the repo is not
confidential, you can zip it and send me.
-- 
Duy

  reply	other threads:[~2012-02-07 12:57 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 [this message]
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=CACsJy8DtmQLX+Lfng-QRzVg9sfo8gQMXB-xTtPYpt+R2gModTg@mail.gmail.com \
    --to=pclouds@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --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 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.