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

Re: Fix archive-destroying "git repack -a -d" bug

From
Linus Torvalds <torvalds@osdl.org>
Date
Sep 18, 2005, 17:00 UTC
Message-ID
<Pine.LNX.4.58.0509180958310.26803@g5.osdl.org>
In-Reply-To
<20050918031837.GB23405@redhat.com>
On Sat, 17 Sep 2005, Dave Jones wrote:
Show 6 quoted lines
> 
> Hmm, I'm sure I've done this several times in my x86info git repo
> (http://www.codemonkey.org.uk/projects/x86info/x86info.git)
> 
> It seems to look ok to git-fsck-cache though. Would that pick up
> any breakage if present ?

It will literally remove every single object in the system, so yes, there would be major breakage. Even "git log" won't work.

Note: this only happens if you haven't done _anything_ in between repacks. 
If you commit anything or do anything else to cause the list of objects to 
change, "git repack" is fine.
			Linus
Previous: Dave JonesNext: Junio C Hamano
Message 3 of 4 in “Fix archive-destroying "git repack -a -d" bug”
  1. Linus TorvaldsSep 18, 2005
  2. Dave JonesSep 18, 2005
  3. Linus TorvaldsSep 18, 2005
  4. Junio C HamanoSep 18, 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.