update comments to point to conversion docs

want to avoid use of -c annex.largefiles..
This commit is contained in:
Joey Hess 2020-01-01 14:38:40 -04:00
parent fb04cfd0e6
commit d0f3b01c31
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
3 changed files with 2 additions and 31 deletions

View file

@ -3,10 +3,6 @@
subject="""Re: Move file from git annex to just git in one commit"""
date="2019-09-30T17:29:39Z"
content="""
git annex unlock MYFILE
git -c annex.largefiles=nothing add MYFILE
git commit -n MYFILE
(The -n is only needed with git-annex older than 7.20190912 but will work
with newer versions too.)
See [[tips/largefiles]], it has recipes for conversion from annex to git and
from git to annex.
"""]]

View file

@ -1,17 +0,0 @@
[[!comment format=mdwn
username="Dwk"
avatar="http://cdn.libravatar.org/avatar/65fade4f1582ef3f00e9ad6ae27dae56"
subject="annexed -> normal git does not work if annexed file was unlocked"
date="2019-10-05T01:45:14Z"
content="""
The sequence of commands given to shift an unlocked annexed file to normal git (for instance a file annexed by mistake due to the new git-add behaviour), namely
git annex unlock file
git -c annex.largefiles=nothing add file
git commit file
does not work if the file is unmodified, as git sees no change to commit. In this case, I believe one should replace the first command with
git annex unannex file
"""]]

View file

@ -1,8 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""Re: annexed -> normal git does not work if annexed file was unlocked"""
date="2019-10-08T18:14:45Z"
content="""
Touching the file first avoids the problem, or git rm --cached to force
git to re-add it. I've updated the example.
"""]]