Added a comment
This commit is contained in:
parent
3aec7db42e
commit
f6222bc6c4
1 changed files with 18 additions and 0 deletions
|
@ -0,0 +1,18 @@
|
|||
[[!comment format=mdwn
|
||||
username="amindfv@6f75355c5dad3450ed73d1f01715be90dfdd6cd6"
|
||||
nickname="amindfv"
|
||||
avatar="http://cdn.libravatar.org/avatar/9cdda587f634ea9a85b34b25be421676"
|
||||
subject="comment 28"
|
||||
date="2019-10-23T04:42:36Z"
|
||||
content="""
|
||||
> Several commenters seem to be under the misapprehension that git add of a modified file that is stored in git before will annex the new version. It does not.
|
||||
|
||||
For what it's worth, this wasn't a misapprehension that I had in my posts above. It's possible I conflated or wasn't clear enough about other concerns in a way that created that impression (or maybe you simply weren't talking about my posts!), but my concerns are about:
|
||||
|
||||
- Loss of control of what's added to git vs. git-annex
|
||||
- Violating the Principle of Least Astonishment
|
||||
- Too much \"magic\" requiring me to work against, instead of with, my tools
|
||||
- Breaking my and others' existing git-annex workflows
|
||||
|
||||
All of which are relevant to adding new files to the repo.
|
||||
"""]]
|
Loading…
Add table
Reference in a new issue