--- /dev/null
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2023-10-23T17:48:54Z"
+ content="""
+I wish it were possible to make `git add` add files in a locked state.
+However, the smudge/clean interface git-annex uses to hook into `git add`
+makes it impossible to do that.
+
+This is why the documentation refers to "git-annex commands", which does
+exclude `git add`. I've made that a little bit more explicit.
+"""]]
looks like "/annex/objects/...". So if you open a file and see
that, you'll need to use `git annex get`.
-Under the hood, unlocked files use git's [[todo/smudge]] filter interface,
+Under the hood, unlocked files use git's smudge/clean filter interface,
and git-annex converts between the content of the big file and a pointer
file, which is what gets committed to git.
By default, git-annex commands will add files in locked mode,
unless used on a filesystem that does not support symlinks, when unlocked
mode is used. To make them always use unlocked mode, run:
-`git config annex.addunlocked true`
+`git config annex.addunlocked true`
+`git add` always adds files in unlocked mode.
"""]]
## adjusted branches