git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Philippe Lhoste <PhiLho@GMX.net>
To: bazaar@lists.canonical.com
Cc: info-cvs@gnu.org, mercurial@selenic.com, git@vger.kernel.org,
	users@tomcat.apache.org
Subject: Re: vcs for hefty video and graphics files
Date: Tue, 23 Nov 2010 11:37:46 +0100	[thread overview]
Message-ID: <icg5ia$5an$1@dough.gmane.org> (raw)
In-Reply-To: <877hg55iyd.fsf@newsguy.com>

On 22/11/2010 19:09, Harry Putnam wrote:
> Which of the main contenders:  cvs subversion mercurial git bizarre
> Maybe  a few more I don't know about, would be the best candidate for
> the usage and user described

bizarre? Never heard of this VCS before...

 > Each project would only run a month or 2 months at the most and then
 > all but the final delivered version would be deleted.  That version
 > might be keep for a yr or so.

Maybe it is pure heresy, but since all you want is to keep temporarily several very big 
and nearly incompressible files where diffs (or deltas?) are probably not significant, I 
would advance that a VCS won't be very useful here.
Advantages of VCS are (among others):
- make delta of changes to keep as little data as possible
- compress this data (?)
- keep changes indefinitely to be sure to have them when we need them
- share and merge (changes from somebody else, or you elsewhere)
Unless I missed something, these advantages doesn't seem to apply there.

Some game makers keep track of their (large) binary files, along with the rest of the 
project (source code). Rarely in isolation.
Perforce and PlasticSCM both boast superior support of these files, I won't comment on 
these allegations (over other VCS), just having no experience here.

Somehow, in your case, the good old way of keeping copies renamed to keep the version (or 
kept in specific directories) might work for you... Perhaps along with a small text file 
with comments on content of each file.

PS.: I don't see why you included Tomcat list...

-- 
Philippe Lhoste
--  (near) Paris -- France
--  http://Phi.Lho.free.fr
--  --  --  --  --  --  --  --  --  --  --  --  --  --

  reply	other threads:[~2010-11-23 10:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-22 18:09 vcs for hefty video and graphics files Harry Putnam
2010-11-23 10:37 ` Philippe Lhoste [this message]
2010-11-23 16:19   ` Harry Putnam
2010-11-23 20:41   ` Jonathan Nieder
2010-11-24 22:42     ` Jakub Narebski
2010-11-25  2:21       ` Jonathan Nieder
2010-11-25 17:34 ` Stefan Monnier

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='icg5ia$5an$1@dough.gmane.org' \
    --to=philho@gmx.net \
    --cc=bazaar@lists.canonical.com \
    --cc=git@vger.kernel.org \
    --cc=info-cvs@gnu.org \
    --cc=mercurial@selenic.com \
    --cc=users@tomcat.apache.org \
    /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).