git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 20, 2008, 20:17 UTC
Message-ID
<7vbq6b4c27.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20080220151017.17840.qmail@767a223c93e1c8.315fe32.mid.smarden.org>
Gerrit Pape <pape@smarden.org> writes:
Show 6 quoted lines
> 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@gitster.siamese.dyndns.org>
Previous: Johannes Schindelin
Message 3 of 3 in “git-clone.sh: properly configure remote even if remote's head is dangling”
  1. git-clone.sh: properly configure remote even if remote's head is danglingGerrit Pape, Feb 20, 2008
  2. Johannes SchindelinFeb 20, 2008
  3. Junio C HamanoFeb 20, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.