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

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

From
Junio C Hamano <junkio@cox.net>
Date
Sep 14, 2005, 18:16 UTC
Message-ID
<7vpsrbjz0t.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20050914124206.GC24405@master.mivlgu.local>
Sergey Vlasov <vsu@altlinux.ru> writes:
Show 6 quoted lines
> The problem is caused by the behavior of fetch.c:process_commit() - it
> skips parent commits which already exist locally.  This is a good
> optimization if your repository is OK, but after an interrupted fetch
> there will be some missing objects in the object tree; the only way to
> find them is to scan the whole tree, so stopping at the existing
> commits is wrong.

Hmph. I could almost swear that I've seen the 'recovery' fix from Daniel and merged it some time ago -- but I do not see that in the git-whatchanged output. The only '--recover' I see is the leftover command line option description to recover from delta-fetch failure, which would not happen because we do not have deltified objects anymore.

Thanks for the patch.
Previous: Sergey VlasovNext: Linus Torvalds
Message 6 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.