File: replacing_a_locked_file_without_unlocking_first.mdwn

package info (click to toggle)
git-annex 10.20230126-3
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 69,344 kB
  • sloc: haskell: 74,654; javascript: 9,103; sh: 1,304; makefile: 203; perl: 136; ansic: 44
file content (1 line) | stat: -rw-r--r-- 473 bytes parent folder | download | duplicates (4) 
1
 
If I want to replace a locked file with new content, rather than edit the existing content, is it ok to skip the [[`git-annex-unlock`|git-annex-unlock]]/[[`git-annex-lock`|git-annex-lock]] steps?  If I just remove the symlink to the annex, create a new regular file in its place, then [[`git-annex-add`|git-annex-add]] the new file and commit, things seem to work fine.   Does this create some inconsistency that can come back to bite me later, or is this supported usage?