# Prevent that real files are committed, only accept symlinks. #!/bin/sh # automatically configured by git-annex
In my case it's not too complex, because I only store "big files" To prevent myself from making such mistakes, I set up a git pre-commit hook. To fix such a mistake if you discover it too late. You ruin the whole point of using git annex, and it is very hard Than the normal git repo, and only storing symlinks in the git repo.īottom line: if you accidentally use git add instead of git annex add In contrast, git annex does its magic by storing the content in a different place Will end up on all clones, even if you remove it in later commits. This means that this content will be recorded in the git history and You'll store the content in the git repo, instead of the git-annex extension of it. If you forget it (not unlikely if git add is baked in your muscle memory), You have to be careful not to forget the annex To add files to a git annex repo, you have to use git annex add $filename My repo covers more than 300GB in pictures and videos in total,īut only 14GB of that is present on my laptop's disk at the moment. Without requiring that all content is present everywhere. Like that I can sync a whole tree of files between multiple devices/backends It's a nerdy solution (a fair amount of git knowledge is required), but I The problem (and solution) described below are not that relevant anymore.įor managing my photo (and video) collection, which is too large to fit
#GIT ANNEX COMMANDS UPDATE#
UPDATE Oct 2019: since the recent v7 repository version of git annex,
0 kommentar(er)
