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

Re: Potentially dangerous behavior of git gc

From
Miklos Vajna <vmiklos@frugalware.org>
Date
Oct 19, 2009, 11:21 UTC
Message-ID
<20091019112153.GX6115@genesis.frugalware.org>
In-Reply-To
<loom.20091019T095725-840@post.gmane.org>
On Mon, Oct 19, 2009 at 08:04:58AM +0000, Sergio Callegari <sergio.callegari@gmail.com> wrote:
Show 5 quoted lines
> With this when the alternate info of A is finally updated, A is broken, missing
> many references and not having a head anymore.
> 
> Would it be better to have git gc not to take dangerous actions on potentially
> problematic repos?

Such repos are usually created using git clone -s. See the NOTE of the manpage under the -s option, probably you want to use git repack -a after git clone.

Previous: Sergio CallegariNext: Sergio
Message 2 of 3 in “Potentially dangerous behavior of git gc”
  1. Sergio CallegariOct 19, 2009
  2. Miklos VajnaOct 19, 2009
  3. SergioOct 20, 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.