File: comment_3_c6ad0934136448a014f6b1c317bba3e6._comment

package info (click to toggle)
git-annex 10.20250416-2
  • links: PTS, VCS
  • area: main
  • in suites: trixie
  • size: 73,572 kB
  • sloc: haskell: 90,656; javascript: 9,103; sh: 1,469; makefile: 211; perl: 137; ansic: 44
file content (15 lines) | stat: -rw-r--r-- 529 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
[[!comment format=mdwn
 username="joey"
 subject="""comment 3"""
 date="2022-09-20T17:37:53Z"
 content="""
I think that the documentation of [[git-annex-unlock]] is pretty clear
about this:

       Unlocking a file changes how it is stored in the git repository
       (from a symlink to a pointer file), so this command will make
       a change that you can commit.

To get the equivilant of the old direct mode, where files are unlocked in
one repository without affecting other clones, use `git-annex adjust --unlock`.
"""]]