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

Re: Remove "historical" objects from repository to save place

From
Junio C Hamano <junkio@cox.net>
Date
Jan 21, 2006, 20:25 UTC
Message-ID
<7virsdl44q.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20060121200615.GM28365@pasky.or.cz>
Petr Baudis <pasky@suse.cz> writes:
Show 5 quoted lines
>> You might be able to cauterize the history at a specific commit
>> and then re-clone.  I've talked about how in "[QUESTION] about
>> .git/info/grafts file" thread yesterday, so I won't repeat that.
>
> Shouldn't the git-prune be sufficient after cauterizing the history?
Logically yes, but practically no.

Most likely what the original requestor cloned from Linus has been already packed so git-prune would not do much.

Previous: Petr BaudisNext: Randal L. Schwartz
Message 4 of 8 in “Remove "historical" objects from repository to save place”
  1. Andrey BorzenkovJan 21, 2006
  2. Junio C HamanoJan 21, 2006
  3. Petr BaudisJan 21, 2006
  4. Junio C HamanoJan 21, 2006
  5. Randal L. SchwartzJan 21, 2006
  6. Junio C HamanoJan 21, 2006
  7. Andrey BorzenkovJan 21, 2006
  8. Andrey BorzenkovJan 21, 2006

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.