diff options
| author |  Joey Hess <joey@kitenet.net> | 2014-02-10 12:01:10 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2014-02-10 12:01:10 -0400 |
| commit | 5cec5d9d7cd40e5bd9ba488ee544b55a9c57cdf5 (patch) | |
| tree | dd7a70c28b838b0075e2eceed335cfec9432ba7b | |
| parent | 1336c87ce9e0fcd4228434e42700211b0a1feb23 (diff) | |
update for direct mode
| -rw-r--r-- | doc/how_it_works.mdwn | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/how_it_works.mdwn b/doc/how_it_works.mdwn index 0acf20565..d91af8309 100644 --- a/doc/how_it_works.mdwn +++ b/doc/how_it_works.mdwn @@ -12,7 +12,8 @@ names of the files and some other metadata remain there. The contents of the files are kept by git-annex in a distributed key/value store consisting of every clone of a given git repository. That's a fancy way to say that git-annex stores the actual file content somewhere under -`.git/annex/`. (See [[internals]] for details.) +`.git/annex/`. (See [[internals]] for details and note that in +[[direct_mode]] the file contents are left in the work tree.) That was the values; what about the keys? Well, a key is calculated for a given file when it's first added into git-annex. Normally this uses a hash |