Dear Git fellows,
from plenty of web searches, I'm aware of Git's limitations regarding large
binary files and Git LFS as a possible solution, but have not yet tried
this myself, with or without LFS. Please allow me a question in the
"opposite" direction:
My goal is to obtain a very simple backup system for typical JPEG photos.
Each photo is a few MB in size and there are several thousands of them.
What I would like to do is put them into a Git repository.
Some thoughts:
- The main purpose and intention is of course to use a central Git
repository and to use Git in order to distribute newly added photos to all
"client systems" in a simple manner.
- The repository would be "add only" and "write once": Each photo is
added only once and quasi never deleted and never modified later.
- It's OK for me that the .git folder roughly takes the same disk volume
than the photos itself. ("roughly same" due to the add-only nature)
- I'm aware of
http://stackoverflow.com/questions/7102053/git-pull-without-remotely-compressing-objects
I regularly use Git for normal use in several software projects, but know
of Git's limitations regarding large binary files and Git LFS only from web
searches and have no related experience.
It seems to me that the problems with large binary files are mostly related
to scenarios as they occur e.g. in game development projects, that is, any
context where files are much larger than photos and change frequently. I
can imagine that in such cases the bandwidth (for cloning), the storage
(for full history), Git's diff and delta computations all become very
problematic.
I would be very happy if you could share some thoughts or insights about
this.
Why is handling large binary data slow in the first place?
With an "add only" repository, does Git LFS have any advantages at all?
Given the above "photo backup" special-case for large binary files, is it
expected to experience the same problems that are primarily addressed with
Git LFS?
Any input would very much be appreciated!
Best regards,
Carsten
--
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.
