From 3a9248385195213806e117843533d33d94eb0104 Mon Sep 17 00:00:00 2001 From: "rrnewton@63c9faa1997c908b1dc04dfdca33c809660cd158" Date: Mon, 21 May 2018 05:29:06 +0000 Subject: [PATCH] Added a comment: Flag to force same behavior as annex.largefiles attribute? --- ...mment_1_3286fb304f161df9775366db27cf9530._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/git-annex-add/comment_1_3286fb304f161df9775366db27cf9530._comment diff --git a/doc/git-annex-add/comment_1_3286fb304f161df9775366db27cf9530._comment b/doc/git-annex-add/comment_1_3286fb304f161df9775366db27cf9530._comment new file mode 100644 index 0000000000..f752bbbf9f --- /dev/null +++ b/doc/git-annex-add/comment_1_3286fb304f161df9775366db27cf9530._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="rrnewton@63c9faa1997c908b1dc04dfdca33c809660cd158" + nickname="rrnewton" + avatar="http://cdn.libravatar.org/avatar/638acc3e55c2bb09aa0dcca5b5c8acb6" + subject="Flag to force same behavior as annex.largefiles attribute?" + date="2018-05-21T05:29:06Z" + content=""" +When in [direct mode](https://git-annex.branchable.com/direct_mode), the \"add the non-large file directly to the git repository\" behavior described above is very useful, because the option of typing simply `git add foo`, does not exist as it does in [indirect mode](https://git-annex.branchable.com/git-annex-indirect/). + +However, I can't see any combination of flags that trigger this behavior. I suppose it can be accomplished by temporarily setting [annex.largefiles](https://git-annex.branchable.com/tips/largefiles/) to a huge value before executing `git annex add` (i.e. creating a `.gitattributes` and then deleting it). I think I'll try that as a work-around, but it would be great to have a flag that accomplishes this. + +"""]]