From: Chris Packham <judge.packham@gmail.com>
To: Peng Yu <pengyu.ut@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: changing files and large files
Date: Fri, 7 May 2010 14:08:27 -0700 [thread overview]
Message-ID: <r2ha038bef51005071408z38f7845bwfca893cafe268ec3@mail.gmail.com> (raw)
In-Reply-To: <j2v366c6f341005071207x7cba4b50jcb9dd3f2c2872a62@mail.gmail.com>
Hi,
On Fri, May 7, 2010 at 12:07 PM, Peng Yu <pengyu.ut@gmail.com> wrote:
> 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.
prev parent reply other threads:[~2010-05-07 21:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 19:07 changing files and large files Peng Yu
2010-05-07 21:08 ` Chris Packham [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=r2ha038bef51005071408z38f7845bwfca893cafe268ec3@mail.gmail.com \
--to=judge.packham@gmail.com \
--cc=git@vger.kernel.org \
--cc=pengyu.ut@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).