summaryrefslogtreecommitdiff
path: root/doc/direct_mode.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2012-12-12 19:20:38 -0400
committerGravatar Joey Hess <joey@kitenet.net>2012-12-12 19:20:38 -0400
commit3e55a8f164d67d5bd1ef86ae2f38fb2c6c3a51b2 (patch)
treea3115943cd1b5a86f9419a8042f469655234937a /doc/direct_mode.mdwn
parentdb6cbec803a17d8e7eebdd3443713b8ea6ddb091 (diff)
direct mode committing
Diffstat (limited to 'doc/direct_mode.mdwn')
-rw-r--r--doc/direct_mode.mdwn11
1 files changed, 6 insertions, 5 deletions
diff --git a/doc/direct_mode.mdwn b/doc/direct_mode.mdwn
index 552725249..095f15d5a 100644
--- a/doc/direct_mode.mdwn
+++ b/doc/direct_mode.mdwn
@@ -20,11 +20,9 @@ deleted or modified at any time). To do so: `git annex untrust .`
## use a direct mode repository
-You can use `git annex add` to add files to your direct mode repository.
-
-The main command that's supported in direct mode repositories is
-`git annex sync`. This automatically commits all changed files to git,
-pushes them out, pulls down any changes, etc.
+The main command that's used in direct mode repositories is
+`git annex sync`. This automatically adds new files, commits all
+changed files to git, pushes them out, pulls down any changes, etc.
You can also run `git annex get` to transfer the content of files into your
direct mode repository. Or if the direct mode repository is a remote of
@@ -39,6 +37,9 @@ You can use `git log` and other git query commands.
## what doesn't work in direct mode
+Don't use `git annex add` -- it thinks all direct mode files are unlocked,
+and locks them.
+
In general git-annex commands will only work in direct mode repositories on
files whose content is not present. That's because such files are still
represented as symlinks, which git-annex commands know how to operate on.