Added a comment
This commit is contained in:
parent
3d677c0990
commit
daa1fa72ef
1 changed files with 10 additions and 0 deletions
|
@ -0,0 +1,10 @@
|
||||||
|
[[!comment format=mdwn
|
||||||
|
username="Ilya_Shlyakhter"
|
||||||
|
avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
|
||||||
|
subject="comment 7"
|
||||||
|
date="2019-10-07T18:20:21Z"
|
||||||
|
content="""
|
||||||
|
Related: [[todo/addunlocked_config_setting]].
|
||||||
|
|
||||||
|
Re: this thread, I also think preserving `git add` default behavior (adding to git) is better. I'm not sure it should *always* add to git. The whole point of v7 was, as I understand it, to make it possible to use normal git workflow (`git add`; `git commit`; [make changes]; `git add`; `git commit`) with large files without thinking about it. Existing scripts that just call `git add` and are unaware of `git-annex-add` would still work. So it makes sense to let `git add` add to annex *when explicitly configured*. In my use case, I'd like to configure it so that any files it adds to the annex are added as locked by default.
|
||||||
|
"""]]
|
Loading…
Reference in a new issue