GitHub recently announced a Git Large File Storage (LFS) [1,2] which uses clean and smudge [3] to transparently sync any large files you actually use without requiring you to download other versions of these files that you don't need (e.g. until you checkout a commit that references a particular large file, you don't get a local copy of that file). This is similar to existing work like git-annex [4], git-fat [5], git-media [6], git-bigstore [7], …. There are minor differences in all these options, but a bunch of overlap too, mostly because folks have trouble keeping track of this space and feel like it's easier to just roll your own [8]. Technical overlap aside, I expect git-lfs will do well simply because it's got GitHub behind it, and anything that GitHub makes easy to do has a big advantage over other systems (for example, SWC uses a fair amount of Jekyll, and the main argument for Jekyll is that GitHub will run it for you). Anyhow, if you use GitHub, want to version control large files, and haven't felt like setting up any of the other options, Git LFS may hit your sweet spot ;).
Cheers, Trevor [1]: https://github.com/blog/1986-announcing-git-large-file-storage-lfs [2]: https://git-lfs.github.com/ [3]: https://github.com/github/git-lfs/blob/master/docs/spec.md#intercepting-git [4]: https://git-annex.branchable.com/ [5]: https://github.com/jedbrown/git-fat [6]: https://github.com/alebedev/git-media [7]: https://github.com/lionheart/git-bigstore [8]: https://news.ycombinator.com/item?id=9345137 -- This email may be signed or encrypted with GnuPG (http://www.gnupg.org). For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
