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

Re: repo corruption - Egit's fault?

From
ESEugene Sajine <euguess@gmail.com>
Date
Dec 18, 2009, 18:30 UTC
Message-ID
<76c5b8580912181030k56cb7dd7l811c0a0d4773d309@mail.gmail.com>
In-Reply-To
<20091218181613.GA10687@spearce.org>
Show 8 quoted lines
> To prevent this in the future, you can force a server to check during
> push by enabling receive.fsckObjects in the server repository's
> configuration file.  A broken EGit client will have the push
> rejected immediately.
>
> --
> Shawn.
>
Thank you for prompt answer, Shawn!

The problem is that as i'm maintaining multiple repos and their quantity will grow i would need to apply this setting site wide. Do you know if i can specify this service for git daemon? It seems like in git deamon docs this service is not listed, but just in case the docs are not up to date... I really don't want to set this up for every repo manually...

Thanks, Eugene

Previous: Shawn O. PearceNext: Eugene Sajine
Message 3 of 4 in “repo corruption - Egit's fault?”
  1. Eugene SajineDec 18, 2009
  2. Shawn O. PearceDec 18, 2009
  3. Eugene SajineDec 18, 2009
  4. Eugene SajineDec 18, 2009

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.