git-annex/doc/git-annex-direct.mdwn

# NAME

git-annex direct - switch repository to direct mode

# SYNOPSIS

git annex direct

# DESCRIPTION

Switches a repository to use direct mode, where rather than symlinks to
files, the files are directly present in the repository.
  
As part of the switch to direct mode, any changed files will be committed.

Note that git commands that operate on the work tree will refuse to
run in direct mode repositories. Use `git annex proxy` to safely run such
commands.

Note that the direct mode/indirect mode distinction is removed in v6
git-annex repositories. In such a repository, you can
use [[git-annex-unlock]](1) to make a file's content be directly present.

# SEE ALSO

[[git-annex]](1)

[[git-annex-indirect]](1)

[[git-annex-unlock]](1)

# AUTHOR

Joey Hess <id@joeyh.name>

Warning: Automatically converted into a man page by mdwn2man. Edit with care.
separated man pages for all the setup commands while at the gate in ATL 2015-03-23 22:20:42 +00:00			`# NAME`

			`git-annex direct - switch repository to direct mode`

			`# SYNOPSIS`

			`git annex direct`

			`# DESCRIPTION`

			`Switches a repository to use direct mode, where rather than symlinks to`
			`files, the files are directly present in the repository.`

			`As part of the switch to direct mode, any changed files will be committed.`

			`Note that git commands that operate on the work tree will refuse to`
			run in direct mode repositories. Use `git annex proxy` to safely run such
			`commands.`

don't let git-annex direct be run in a v6 repo 2015-12-04 20:29:27 +00:00			`Note that the direct mode/indirect mode distinction is removed in v6`
			`git-annex repositories. In such a repository, you can`
			`use [[git-annex-unlock]](1) to make a file's content be directly present.`

separated man pages for all the setup commands while at the gate in ATL 2015-03-23 22:20:42 +00:00			`# SEE ALSO`

			`[[git-annex]](1)`

expand manpages cross-references significantly i found that most man pages only had references to the main git-annex manpage, which i stillfind pretty huge and hard to navigate through. i tried to sift through all the man pages and add cross-references between relevant pages. my general rule of thumb is that links should be both ways unless one of the pages is a more general page that would become ridiculously huge if all backlinks would be added (git-annex-preferred-content comes to mind). i have also make the links one per line as this is how it was done in the metadata pages so far. i did everything but the plumbing, utility and test commands, although some of those are linked from the other commands so cross-links were added there as well. 2015-05-29 16:12:55 +00:00			`[[git-annex-indirect]](1)`

don't let git-annex direct be run in a v6 repo 2015-12-04 20:29:27 +00:00			`[[git-annex-unlock]](1)`

separated man pages for all the setup commands while at the gate in ATL 2015-03-23 22:20:42 +00:00			`# AUTHOR`

			`Joey Hess <id@joeyh.name>`

			`Warning: Automatically converted into a man page by mdwn2man. Edit with care.`