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

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

From
Daniel Barkalow <barkalow@iabervon.org>
Date
Sep 14, 2005, 20:55 UTC
Message-ID
<Pine.LNX.4.63.0509141641290.23242@iabervon.org>
In-Reply-To
<Pine.LNX.4.58.0509141325310.26803@g5.osdl.org>
On Wed, 14 Sep 2005, Linus Torvalds wrote:
Show 9 quoted lines
> On Wed, 14 Sep 2005, Junio C Hamano wrote:
> > 
> > Thanks for the patch.
> 
> This is wrong.
> 
> Any "fetch" logic that writes the refs before all the objects are gathered 
> is _buggy_. It's not about "recovery", it should never do that in the 
> first place.

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. We probably want to keep a cache listing some commits we have, and use that.

	-Daniel
*This .sig left intentionally blank*
Previous: Junio C HamanoNext: Linus Torvalds
Message 9 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.