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

Re: Is there a way to control the number of revisions will be saved by git

From
AArafangion <thestar@fussycoder.id.au>
Date
Dec 3, 2008, 11:37 UTC
Message-ID
<1228304226.23167.8.camel@therock.nsw.bigpond.net.au>
In-Reply-To
<2f5ea7490812030301p29e944fw5f59943dc352cd09@mail.gmail.com>

On Wed, 2008-12-03 at 13:01 +0200, Tzury Bar Yochay wrote: <snip>

> Say I wish to save only 100 generations back (per branch).
> Is it possible to configure git so it will save only N records back.

What would be the advantage in doing that? Git is designed so that you have all your history available, and saves data in such a way that it really doesn't take much space.

How would git be able to perform a merge from one branch to another if it didn't have this history available?

That said, you could probably chop off the history you don't want by doing tricks with grafting, and rewriting all your history, but this would likely use more disk space because your branches wouldn't have anything in common, and also make it very difficult to merge in the future.

Previous: Miklos VajnaNext: Jean-Luc Herren
Message 5 of 9 in “Is there a way to control the number of revisions will be saved by git”
  1. Tzury Bar YochayDec 3, 2008
  2. Johannes SixtDec 3, 2008
  3. Jakub NarebskiDec 3, 2008
  4. Miklos VajnaDec 3, 2008
  5. ArafangionDec 3, 2008
  6. Jean-Luc HerrenDec 3, 2008
  7. Tzury Bar YochayDec 3, 2008
  8. Tzury Bar YochayDec 3, 2008
  9. Tzury Bar YochayDec 3, 2008

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.