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

Re: git-clone still broken wrt. unpacking working tree with http transport

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 6, 2008, 23:30 UTC
Message-ID
<7vve0mqgz9.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<32A340A4-BB0C-4D0E-9B8D-A4FCEA4B24D1@rapleaf.com>
Kevin Ballard <kevin@rapleaf.com> writes:
Show 5 quoted lines
> No I didn't. I guess it's just bad luck that 541fc218 was committed a
> few hours before I reported the issue ;) I generally git-pull in the
> morning, so I pulled before that got committed.
>
> Actually, I ran into it last week but forgot to mention it then.
That's Ok.  I tried this locally and it seems to work ;-)
Previous: Kevin Ballard
Message 4 of 4 in “git-clone still broken wrt. unpacking working tree with http transport”
  1. Kevin BallardJun 5, 2008
  2. Jeff KingJun 6, 2008
  3. Kevin BallardJun 6, 2008
  4. Junio C HamanoJun 6, 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.