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

Re: [PATCH] Fix fetch completeness assumptions

From
Junio C Hamano <junkio@cox.net>
Date
Sep 17, 2005, 08:32 UTC
Message-ID
<7vacicccxl.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<7vhdckceas.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> writes:
Show 7 quoted lines
> Daniel Barkalow <barkalow@iabervon.org> writes:
>
>> Don't assume that any commit we have is complete; assume that any ref
>> we have is complete.
>
> Have you tested this idea with cloning into an empty repository?
> It seems to break my tests.

Sorry, I spoke too fast. This is not _broken_ per se, but is just slow.

I tried to clone http://kernel.org/pub/scm/git.git/; bulk of the objects are packed there but the new code is _too_ cautious, since it did not have any refs to begin with, it ended up walking the commits in the already downloaded packs to the root.

Previous: Junio C HamanoNext: Junio C Hamano
Message 8 of 11 in “Fix fetch completeness assumptions”
  1. Fix fetch completeness assumptionsDaniel Barkalow, Sep 15, 2005
  2. Junio C HamanoSep 15, 2005
  3. Daniel BarkalowSep 15, 2005
  4. Sergey VlasovSep 15, 2005
  5. Daniel BarkalowSep 15, 2005
  6. Junio C HamanoSep 16, 2005
  7. Junio C HamanoSep 17, 2005
  8. Junio C HamanoSep 17, 2005
  9. Help cloning over http.Junio C Hamano, Sep 17, 2005
  10. Daniel BarkalowSep 17, 2005
  11. Improve the safety check used in fetch.cJunio C Hamano, Sep 18, 2005

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.