diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2015-12-27 17:27:52 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2015-12-27 17:27:52 -0400 |
| commit | ca407b7328105bc3baa6625569b1d3a29375e18e (patch) | |
| tree | 5ee8614abb1247a570231e992f3978d0c097a3b5 | |
| parent | f59c81c380147cfaff60b49b0cb816c610ace7f5 (diff) | |
cleanup
| -rw-r--r-- | doc/tips/unlocked_files.mdwn | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/doc/tips/unlocked_files.mdwn b/doc/tips/unlocked_files.mdwn index b510dd2f4..0e9b9da92 100644 --- a/doc/tips/unlocked_files.mdwn +++ b/doc/tips/unlocked_files.mdwn @@ -9,12 +9,11 @@ want to lose it in a fumblefingered mistake. bash: some_file: Permission denied Sometimes though you want to modify a file. Maybe once, or maybe -repeatedly. To modify an annexed file, you have to first unlock it, +repeatedly. To modify a locked file, you have to first unlock it, by running `git annex unlock`. # git annex unlock some_file # echo "new content" > some_file - # Back before git-annex version 6, and its v6 repository mode, unlocking a file like this was a transient thing. You'd modify it and then `git annex add` the @@ -32,7 +31,7 @@ had many problems of its own. ## enter v6 mode -/!\ This is an experimental feature; see its [[todo_list|todo//smudge]] +/!\ This is an experimental feature; see its [[todo_list|todo/smudge]] for known issues. This led to the v6 repository mode, which makes unlocked files remain |