mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

update

Browse source
This commit is contained in:
Joey Hess 2013-11-07 14:40:34 -04:00
parent fcf019b9ec
commit 62677d3268
1 changed files with 5 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

9
doc/direct_mode.mdwn
View file

@ -69,8 +69,9 @@ direct mode.
As for git commands, direct mode prevents using any git command that would As for git commands, direct mode prevents using any git command that would
modify or access the work tree. So you cannot `git commit` or `git pull` modify or access the work tree. So you cannot `git commit` or `git pull`
(use `git annex sync` for both instead), or run `git status`. (use `git annex sync` for both instead), or run `git status` (use `git
These git commands will complain "fatal: This operation must be run in a work tree". annex status` instead). These git commands will complain "fatal: This
operation must be run in a work tree".
The reason for this is that git doesn't understand how git-annex uses the The reason for this is that git doesn't understand how git-annex uses the
work tree in direct mode. Where git expects the symlinks that get checked work tree in direct mode. Where git expects the symlinks that get checked
@ -78,8 +79,8 @@ into git to be checked out in the work tree, direct mode instead replaces
them with the actual content of files, as managed by git-annex. them with the actual content of files, as managed by git-annex.
There are still lots of git commands you can use in direct mode. For There are still lots of git commands you can use in direct mode. For
example, you can run `git log` on files, run `git push`, `git config`, example, you can run `git log` on files, run `git push`, `git fetch`,
`git remote add` etc. `git config`, `git remote add` etc.
## forcing git to use the work tree in direct mode ## forcing git to use the work tree in direct mode