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

Re: rsync deprecated but promoted?

From
Linus Torvalds <torvalds@osdl.org>
Date
Sep 26, 2005, 17:55 UTC
Message-ID
<Pine.LNX.4.58.0509261038460.3308@g5.osdl.org>
In-Reply-To
<dh98gk$6rp$1@sea.gmane.org>
On Mon, 26 Sep 2005, walt wrote:
Show 13 quoted lines
> 
> Just because you mentioned it, I did a git-fsck-objects on my local
> copies of your kernel tree and Junio's git tree.
> 
>  From git I got this:
> $git-fsck-objects
> missing commit 00d8bbd3c4bba72a6dfd48c2c0c9cbaa000f13c2
> broken link from     tag 02b2acff8bafb6d73c6513469cdda0c6c18c4138
>                to  commit d5bc7eecbbb0b9f6122708bf5cd62f78ebdaafd8
> <similar lines snipped>
> 
>  From your tree I got only this single line:
> dangling commit 02459eaab98a6a57717bc0cacede148fc76af881

That commit shouldn't be dangling, but I suspect it is harmless and is most likely because you have pack-files. Use "git-fsck-cache --full" if you are downloading with http/rsync (since that gets packs without unpacking them, and you haven't re-packed everything).

The git thing may be similar, although it sounds unlikely. A more likely reason is that earlier http pulling got incomplete trees if you ever interrupted it with ^C.

> Yet both trees compile and run perfectly.  Are these messages
> worrisome?  (BTW, git was cloned and updated using http.)

Yes, they can be worrisome. Some of it may be normal (I really suspect that the kernel tree is that kind - a "dangling commit" is almost always either because you've lost a tag or because of a pack-file that wasn't examined).

Your git tree is quote possibly corrupted.

The good news is that if "git checkout" works, then the corruption is all old - you may not have all of the history, but the corruption is "harmless".

There's nothing fundamentally wrong with not having all of history: it will cause fsck to complain (unless you "plug" the history by using a graft file). And obviously it means that you may not be able to go back in time - but you may never even care.

A "git-http-fetch --recover HEAD <url>" _should_ fix it, but I don't think that works right now. It's documented, but it doesn't do anything. Junio?

			Linus
Previous: waltNext: walt
Message 13 of 26 in “rsync deprecated but promoted?”
  1. Zack BrownSep 25, 2005
  2. H. Peter AnvinSep 25, 2005
  3. Martin CoxallSep 25, 2005
  4. Petr BaudisSep 26, 2005
  5. Brian GerstSep 26, 2005
  6. Petr BaudisSep 26, 2005
  7. Brian GerstSep 26, 2005
  8. Linus TorvaldsSep 26, 2005
  9. Petr BaudisSep 26, 2005
  10. Linus TorvaldsSep 26, 2005
  11. Petr BaudisNov 10, 2005
  12. waltSep 26, 2005
  13. Linus TorvaldsSep 26, 2005
  14. waltSep 26, 2005
  15. Johannes SchindelinSep 26, 2005
  16. Junio C HamanoSep 26, 2005
  17. Daniel BarkalowSep 26, 2005
  18. Junio C HamanoSep 26, 2005
  19. Petr BaudisSep 26, 2005
  20. hared GIT repos (was Re: rsync deprecated but promoted?)Matthias Urlichs, Sep 27, 2005
  21. Junio C HamanoSep 27, 2005
  22. Matthias UrlichsSep 27, 2005
  23. Sergey VlasovSep 27, 2005
  24. Matthias UrlichsSep 27, 2005
  25. Linus TorvaldsSep 27, 2005
  26. A Large Angry SCMSep 27, 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.