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

Re: changing files and large files

From
Chris Packham <judge.packham@gmail.com>
Date
May 7, 2010, 21:08 UTC
Message-ID
<r2ha038bef51005071408z38f7845bwfca893cafe268ec3@mail.gmail.com>
In-Reply-To
<j2v366c6f341005071207x7cba4b50jcb9dd3f2c2872a62@mail.gmail.com>
Hi,
On Fri, May 7, 2010 at 12:07 PM, Peng Yu <pengyu.ut@gmail.com> wrote:
Show 6 quoted lines
> I'm considering using file control systems. I'm wondering if git could
> handle the following situations. Would you please let me?
>
> 1. Change file names: whether it records the lineage of files that
> undergoes name changes?
>

Technically it detects renames rather than tracking them explicitly. Other tools (like bazaar or mercurial) track renames explicitly.

> 2. Files are extremely large (of hundred of MB or even GB).
>

Search this list for a more concrete description of where git is at with handling large files. Generally speaking the git tools need to read all of the file into memory to operate so the limit is really the amount of RAM/swap space you have. I think some people on this list do have modified version which handle files that are > than available swap space. Git was designed around tracking source code, which it does really well. If you're wanting to store/track media you may have better luck with a system designed for that.

Previous: Peng Yu
Message 2 of 2 in “changing files and large files”
  1. Peng YuMay 7, 2010
  2. Chris PackhamMay 7, 2010

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.