largefiles: fail-on-unspecified mode?

The imminent move of to v7 of my shared repositories (eg. family photo collection) offers a chance to simplify the workflow from differentiating between git annex commands and git commands for participants who have a hard time keeping them apart using largefiles. In practice, largefiles would be configured to always annex JPEG files, various raw formats and video data, but to never annex data like SVG files (typically collages), .pto files (Hugin's panorama files) or READMEs.

I don't trust the above list to be comprehensive, and want to avoid errors in both directions (needlessly annexed files I'd actually want under regular version control, and worse yet, huge files in the hard-to-edit git history).

Is there (or could there be added) a way I could set files to a "I don't know" state of largefiles (and make that the default for everything not explicitly configured), such that git add would rather err out than making the wrong decision?

Thanks
chrysn

RSS Atom

comment 1

This is a good idea, but unfortunately the interface that git add uses to run git-annex doesn't provide a way for git-annex to request that the file not be added. Even if git-annex exits with an error, git will assume the best thing to do is to add the file itself. As documented in the gitattributes(5) man page:

       A missing filter driver definition in the config, or a filter driver that
       exits with a non-zero status, is not an error but makes the filter a
       no-op passthru.

So this would I think need an extension to git..

However, there is a fairly easy way to convert an annexed file to be stored in git if your annex.largefiles configuration didn't do the right thing:

touch thefile
git -c annex.largefiles=nothing add thefile

Comment by joey — Wed Jan 16 19:11:35 2019

Remove comment

Add a comment