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

Re: git-repack & big files

From
PSPhillip Susi <psusi@cfl.rr.com>
Date
Jan 11, 2011, 15:43 UTC
Message-ID
<4D2C7AA9.1020506@cfl.rr.com>
In-Reply-To
<1294731438.3300.973.camel@voubian.casa>
On 1/11/2011 2:37 AM, Pietro Battiston wrote:
Show 6 quoted lines
> Since it perfectly does what it is not optimized to do... I then wonder
> when it does not do what it declares: if I run git-repack² with the
> parameter --window-memory set to, for instance, "100m", it takes
> hundreds and hundreds of MB of memory until it runs out of memory, fails
> a malloc and aborts.
> So, two questions:
--window-memory reduces the window size to try and stay under the limit,
 but the window size can not be reduced below 1.
Show 5 quoted lines
> 2) do I have any hope that in one way or another my 500+ MB mailboxes
> with relatively small changes over time are archived smartly (=diffs) by
> git at the current state of development? If I understand correctly, the
> project git-bigfiles³ would just "solve" my problems by not making
> differences of big files.
Git is not a backup tool.  You should use rsync rdiff-backup instead.
Previous: Pietro BattistonNext: Pietro Battiston
Message 2 of 6 in “git-repack & big files”
  1. Pietro BattistonJan 11, 2011
  2. Phillip SusiJan 11, 2011
  3. Pietro BattistonJan 11, 2011
  4. Stephen BashJan 11, 2011
  5. Phillip SusiJan 11, 2011
  6. Pietro BattistonJan 13, 2011

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.