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

Added a comment

Browse source
This commit is contained in:
http://joeyh.name/ 2014-06-04 19:03:05 +00:00 • committed by admin
parent 6ba5df201e
commit 8d9b62a43f
1 changed files with 26 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

26
doc/forum/Revert_to_a_precedent_state_in_direct_mode/comment_1_1ae9f7defbab44621c3108973a4f683a._comment Normal file
View file

@ -0,0 +1,26 @@
[[!comment format=mdwn
username="http://joeyh.name/"
ip="108.236.230.124"
subject="comment 1"
date="2014-06-04T19:03:05Z"
content="""
I wish that I had a good answer for you, but since you're using direct mode, I really do not!
You can run this to see the status:
git -c core.bare=false status
That's safe. Everything below has a good chance of losing data if not used carefully.
You can run a command like this to *delete* an unwanted file (that is shown as a new file in the above).
git -c core.bare=false rm -f unwanted_file
If the status shows a file as being modified, you can run this to throw away the modified version. This does not put back the old version! It will leave you with a broken symlink.
git -c core.bare=false reset modified_file
git -c core.bare=false checkout modified_file
git annex fsck
If you're lucky, you can then `git annex get` to get the old version from some other repository that still has it.
"""]]