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

Re: Auto-repo-repair

From
DNDrew Northup <n1xim.email@gmail.com>
Date
Nov 19, 2012, 03:30 UTC
Message-ID
<CAM9Z-nmu2MiE9vF9T6Aw8vFTR8mTkuR3akHgZX6+=n3uA4fmpA@mail.gmail.com>
In-Reply-To
<66719060-db68-45b4-8453-2fd996f27657@zcs>
On Sun, Nov 18, 2012 at 11:55 AM, Enrico Weigelt <enrico.weigelt@vnc.biz> wrote:
Show 5 quoted lines
>
>> How would the broken repository be sure of what it is missing to
>> request it from the other side?
>
> fsck will find missing objects.

And what about the objects referred to by objects that are missing? Jeff's solution doesn't suffer from this recursivity problem.

-- 
-Drew Northup
--------------------------------------------------------------
"As opposed to vegetable or mineral error?"
-John Pescatore, SANS NewsBites Vol. 12 Num. 59
Previous: Enrico WeigeltNext: Enrico Weigelt
Message 6 of 9 in “Auto-repo-repair”
  1. Enrico WeigeltNov 16, 2012
  2. Jeff KingNov 16, 2012
  3. Enrico WeigeltNov 17, 2012
  4. Drew NorthupNov 18, 2012
  5. Enrico WeigeltNov 18, 2012
  6. Drew NorthupNov 19, 2012
  7. Enrico WeigeltNov 19, 2012
  8. Drew NorthupNov 20, 2012
  9. Enrico WeigeltNov 22, 2012

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.