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

Re: collapsing old git history to reduce repo size, while preserving commit #s and tags

From
SCStas Cherkassky <scherkas@gmail.com>
Date
Oct 30, 2013, 07:52 UTC
Message-ID
<CAJSXqrrMCWmRBoRNCLuD6DvU=CSk+MVGrSOCeOROROEaKouVKQ@mail.gmail.com>
In-Reply-To
<CAJSXqrr7rHxyXX=_+xgJ4FW2UHSts2jRt7zwrkkw1L3uKHnCtw@mail.gmail.com>
Andrew,

Shallow clone (if that's what you meant) is not suitable because it doesn't allow to push/pull to/from this shallow repository.

I understand that generally git is designed to preserve the history. But the problem is real, and probably is not unique to our project. The fact that there ARE some ways to modify history (collapse commits, rebase, filter-branch) made me hopeful that what I need is also possible..

thanks, Stas

Previous: Andrew ArdillNext: Jakub Narębski
Message 3 of 5 in “Re: collapsing old git history to reduce repo size, while preserving commit #s and tags”
  1. Stas CherkasskyOct 29, 2013
  2. Andrew ArdillOct 29, 2013
  3. Stas CherkasskyOct 30, 2013
  4. Jakub NarębskiOct 30, 2013
  5. Duy NguyenOct 30, 2013

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.