From: Jakub Narebski <jnareb@gmail.com>
To: Will Hoag <will@willhoag.com>
Cc: git@vger.kernel.org
Subject: Re: Git for animation studio
Date: Sun, 25 Sep 2011 06:30:08 -0700 (PDT) [thread overview]
Message-ID: <m3sjnkpx75.fsf@localhost.localdomain> (raw)
In-Reply-To: <F533627C-C656-4733-8489-B4F62FE79A91@willhoag.com>
Will Hoag <will@willhoag.com> writes:
> I'm doing researching for an online version control systems for our
> developing studio. Wondering how git could work for us in regards to
> large files, lots of data, lots of collaboration etc. I have a basic
> idea of how it works, but I'm very new to version control. Many
> thanks for your help.
What Git *might* have problems with is large un-deltable binary files;
there are however third party tools that try to deal with this
problem, like git-annex, or git-media (git-bigfiles fork is dead
IIRC).
You can [probably] find more information on tools page of Git
Wiki... when it will be up.
HTH
--
Jakub Narębski
next prev parent reply other threads:[~2011-09-25 13:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-24 21:43 Git for animation studio Will Hoag
2011-09-25 13:30 ` Jakub Narebski [this message]
2011-09-27 9:34 ` Jonathan Nieder
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=m3sjnkpx75.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=will@willhoag.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).