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

Re: [PATCH 0/4] Recovery after interrupted HTTP(s) fetch

From
Linus Torvalds <torvalds@osdl.org>
Date
Sep 14, 2005, 21:15 UTC
Message-ID
<Pine.LNX.4.58.0509141411510.26803@g5.osdl.org>
In-Reply-To
<Pine.LNX.4.63.0509141641290.23242@iabervon.org>
On Wed, 14 Sep 2005, Daniel Barkalow wrote:
Show 5 quoted lines
> 
> It's not about the refs at all. The issue is that, when it reaches a 
> commit that we already have, it assumes that we have everything that 
> commit references and stops there. It really ought to not do that, but I 
> think it might be too slow if it goes through everything all the time.
No, you don't need to go through everything all the time.

Do what the pack-sending stuff does: it assumes that it has everything that is reachable from the _old_ refs. It doesn't walk all the way to the root, it "just" walks far enough that it can ignore anything that was reachable from the old refs.

Yes, it's slightly more complex than assuming "oh, I have this object, so I must have all of its ancestors", but it's a lot safer. Then the rule just becomes: only update refs once you've fetched all the objects.

		Linus
Previous: Daniel BarkalowNext: Daniel Barkalow
Message 10 of 15 in “Recovery after interrupted HTTP(s) fetch”
  1. 0/4 Recovery after interrupted HTTP(s) fetchSergey Vlasov, Sep 14, 2005
  2. 1/4 Do not try to process objects more than once during fetchSergey Vlasov, Sep 14, 2005
  3. 2/4 git-*-fetch: Gracefully recover from retrieval failureSergey Vlasov, Sep 14, 2005
  4. 3/4 git-fetch: Add --recover optionSergey Vlasov, Sep 14, 2005
  5. 4/4 Document git-fetch optionsSergey Vlasov, Sep 14, 2005
  6. Junio C HamanoSep 14, 2005
  7. Linus TorvaldsSep 14, 2005
  8. Junio C HamanoSep 14, 2005
  9. Daniel BarkalowSep 14, 2005
  10. Linus TorvaldsSep 14, 2005
  11. Daniel BarkalowSep 14, 2005
  12. Junio C HamanoSep 14, 2005
  13. Matthias UrlichsSep 15, 2005
  14. Daniel BarkalowSep 15, 2005
  15. Junio C HamanoSep 15, 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.