mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Added a comment: Flag to force same behavior as annex.largefiles attribute?

Browse source
This commit is contained in:
rrnewton@63c9faa1997c908b1dc04dfdca33c809660cd158 2018-05-21 05:29:06 +00:00 • committed by admin
parent 6a0379a056
commit 3a92483851
1 changed files with 12 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
doc/git-annex-add/comment_1_3286fb304f161df9775366db27cf9530._comment Normal file
View file

@ -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.
"""]]