comment
This commit is contained in:
parent
3cc23df35b
commit
3de6dffd36
1 changed files with 15 additions and 0 deletions
|
@ -0,0 +1,15 @@
|
||||||
|
[[!comment format=mdwn
|
||||||
|
username="joey"
|
||||||
|
subject="""comment 8"""
|
||||||
|
date="2019-10-08T18:03:05Z"
|
||||||
|
content="""
|
||||||
|
Candyangel, you missed this part of my comment:
|
||||||
|
|
||||||
|
> But `mv foo bar; git add bar` is normally identical to `git mv foo bar`.
|
||||||
|
> Why should using git-annex break that identity?
|
||||||
|
|
||||||
|
With locked files, that identity still holds; you can mv a symlink and git
|
||||||
|
add it, and you again have an annexed file. So every git and git-annex
|
||||||
|
repository has always behaved that way. There are innumerable workflows and
|
||||||
|
documentation that depend on that, in big or small ways.
|
||||||
|
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue