On Tue, Feb 24, 2015 at 12:06:38PM -0600, Peng Yu wrote:
> I forget to send to the mailing list.
> ---------- Forwarded message ----------
> From: Peng Yu <pengyu...@gmail.com>
> Date: Tue, Feb 24, 2015 at 12:05 PM
> Subject: Re: [git-users] How to use git to store large files without
> keeping track of versions?
> To: Konstantin Khomoutov <flatw...@users.sourceforge.net>
> On Tue, Feb 24, 2015 at 7:45 AM, Konstantin Khomoutov
> <flatw...@users.sourceforge.net> wrote:
> > On Sun, 22 Feb 2015 07:51:59 -0800 (PST)
> > pengyu...@gmail.com wrote:
> >
> >> I have some data files that need to be stored along with source code.
> >> These data files are large, but I don't need to keep their versions.
> >> I only need to keep the versions of the source code.
> >>
> >> git-annex is mainly for large files with versioning. Therefore, it is
> >> not suitable for my situation.
> >>
> >> Does anybody know whether there is a way to use git to manage source
> >> code (with versioning) as well data files (without versioning)?
> >
> > It's a bit unclear what you are really asking for.
> >
> > Are you fine with keeping those files checked into your repository and
> > are just afraid each commit will somehow include those file into the
> > repository again and again (many guides state that with each commit Git
> > stores snapshots, not deltas)?  If so, then fear not: while Git indeed
> > stores snapshots, the content which did not change will not be
> > somehow included again -- the new commit will reference existing
> > objects representing those big files.  So, just add and commit these
> > files once and just make sure you don't change them and commit these
> > changes.
> In my git repository, there are data files as well as source files.
> For source files, they can be stored with the regular git mechanisms.
> The problem is that data files (many of them, each one many MBs). They
> stored in gz files, they can not be effectively diffed as the content
> of the data can be completely changed. Also, old data files can not be
> permanently deleted from the .git directory, even they are not
> available in the most recent commit. This is can be unacceptable
> situation, as the git reposiotry will quickly grow to a size that is
> slow to use.
> Is it clear what my scenario is?

I think git-annex *is* solving exactly this problem!

If you have played with git-annex, would you please explain why it
isn't what you are looking for?


Magnus Therning                      OpenPGP: 0xAB4DFBA4 
email: mag...@therning.org   jabber: mag...@therning.org
twitter: magthe               http://therning.org/magnus

You know, take Lisp. You know, it’s the most beautiful language in the
world. At least up until Haskell came along.
     -- Larry Wall

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Attachment: pgpaK2a9qK1CD.pgp
Description: PGP signature

Reply via email to