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

Added a comment: Adopting "git annex add" as default command in workflow

Browse source
This commit is contained in:
davicastro 2018-03-08 11:21:55 +00:00 • committed by admin
parent f7e2503410
commit 2a67c125e1
1 changed files with 9 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
doc/tips/largefiles/comment_10_18f17926c44ea4b0c17a61a91c6bb5b5._comment Normal file
View file

@ -0,0 +1,9 @@
[[!comment format=mdwn
username="davicastro"
avatar="http://cdn.libravatar.org/avatar/4e708663cf4d5b9e8cfea74caf4307fc"
subject="Adopting "git annex add" as default command in workflow"
date="2018-03-08T11:21:55Z"
content="""
Hi, from technical point of view, are there any drawbacks/limitations on adopting a workflow of everyone in the project using \"git annex add\" and relying on the annex.largefiles settings instead of them having to use the separate commands?
* I would use repo v5 as repo v6 seems to still need work to do, and I don't need it's features. I just would like to avoid human error of people not using by mistake regular git add for bigfiles. I understand that repo v6 would allow, but I don't like it's default behavior of using unlocked mode when I add things with git add (although it would properly annex the files, but in unlocked mode these files would occupy space in the work copy, and I don't want that). Thanks.
"""]]