From 75e530346b3828cf50d8e2104cad14d02f49e6ab Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Mon, 6 Oct 2014 15:36:54 +0000 Subject: [PATCH] Added a comment --- ...t_1_7ce3be5bafd62ce5ed78bcd9323039cc._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/forum/add_only_binary_files__63__/comment_1_7ce3be5bafd62ce5ed78bcd9323039cc._comment diff --git a/doc/forum/add_only_binary_files__63__/comment_1_7ce3be5bafd62ce5ed78bcd9323039cc._comment b/doc/forum/add_only_binary_files__63__/comment_1_7ce3be5bafd62ce5ed78bcd9323039cc._comment new file mode 100644 index 0000000000..e53cb1f0f3 --- /dev/null +++ b/doc/forum/add_only_binary_files__63__/comment_1_7ce3be5bafd62ce5ed78bcd9323039cc._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.54" + subject="comment 1" + date="2014-10-06T15:36:54Z" + content=""" +If you can configure `annex.largefiles` to match only binary files, then `git annex add` will respect it, and only add those files. + +For example, if you were working on a game written in C, and wanted to use git-annex only for the game art, but not the source code, you could configure it: + + git config annex.largefiles 'largerthan=100kb and not (include=*.c or include=*.h)' + +This doesn't currently support looking at the file content to determine eg, its MIME type. That's been suggested as an added feature before. + +More simply, if you `git add` the non-binary files yourself first, `git annex add` will skip over those files and only add the other files. +"""]]