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

response

Browse source
This commit is contained in:
Joey Hess 2016-05-17 14:13:21 -04:00
parent 8006ac923b
commit e81b1bc9e7
Failed to extract signature
1 changed files with 21 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

21
doc/forum/What_am_I_doing_wrong_with_move__63__/comment_1_a49d98426ef8dd17e6cca6b5fba5c9bf._comment Normal file
View file

@ -0,0 +1,21 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2016-05-17T18:04:53Z"
content="""
It sounds like the symlink in the git repository has been changed to point
to some other content that the content it had originally. Since git tracks
past versions of files, you should be able to use `git log` on the file to
find out when this hapened and you can use `git checkout` to check out the
original version of the file, or `git revert` the commit that changed it to
point to the wrong content. The content of the file should still be stored
in the git annex, so you should be able to access it this way.
Now, it kind of sounds like something added the git-annex link for a
file, as it would appear on the FAT filesytem, to git-annex as the new
content of the file. It would certianly be a bug if a git-annex command
did that.
What does `git annex info` (with no other parameters) report when you run it in the repository on
the USB drive? What filesystem is in use on the USB drive?
"""]]