Re: [PATCH] git-clone.sh: properly configure remote even if remote's head is dangling

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Gerrit Pape <pape@xxxxxxxxxxx> writes:

> When cloning a remote repository which's HEAD refers to a nonexistent
> ref, git-clone cloned all existing refs, but failed to write the
> configuration for 'remote'.  Now it detects the dangling remote HEAD,
> refuses to checkout any local branch since HEAD refers to nowhere, but
> properly writes the configuration for 'remote', so that subsequent
> 'git fetch's don't fail.

The patch looks Ok, thanks.

By the way, I am still waiting for an ack/nack to my butchering
of your earlier "hash-object" patch.

  http://thread.gmane.org/gmane.comp.version-control.git/73811/focus=73964
  Message-Id: <7vskzugm8x.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxx>


-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux