git-annex/doc/git-annex-export.mdwn

# NAME

git-annex export - export content to a remote

# SYNOPSIS

git annex export `treeish --to remote`

# DESCRIPTION

Use this command to export a tree of files from a git-annex repository.

Normally files are stored on a git-annex special remote named by their
keys. That is great for data storage, but your filenames are obscured.
Exporting replicates the tree to the special remote as-is.

Mixing key/value and exports in the same remote would be a mess and so is
not allowed. So, you have to configure a remote with `exporttree=yes`
when initially setting it up with [[git-annex-initremote]](1).

Repeated exports are done efficiently, by diffing the old and new tree,
and transferring only the changed files.

Exports can be interrupted and resumed. However, partially uploaded files
will be re-started from the beginning.

# SEE ALSO

[[git-annex]](1)

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

# AUTHOR

Joey Hess <id@joeyh.name>

Warning: Automatically converted into a man page by mdwn2man. Edit with care.
documentation for export This commit was sponsored by Ole-Morten Duesund on Patreon. 2017-08-29 17:25:48 +00:00			`# NAME`

			`git-annex export - export content to a remote`

			`# SYNOPSIS`

			git annex export `treeish --to remote`

			`# DESCRIPTION`

			`Use this command to export a tree of files from a git-annex repository.`

			`Normally files are stored on a git-annex special remote named by their`
			`keys. That is great for data storage, but your filenames are obscured.`
			`Exporting replicates the tree to the special remote as-is.`

			`Mixing key/value and exports in the same remote would be a mess and so is`
implement exporttree=yes configuration * Only export to remotes that were initialized to support it. * Prevent storing key/value on export remotes. * Prevent enabling exporttree=yes and encryption in the same remote. SetupStage Enable was changed to take the old RemoteConfig. This allowed only setting exporttree when initially setting up a remote, and not configuring it later after stuff might already be stored in the remote. Went with =yes rather than =true for consistency with other parts of git-annex. Changed docs accordingly. This commit was supported by the NSF-funded DataLad project. 2017-09-04 16:40:33 +00:00			not allowed. So, you have to configure a remote with `exporttree=yes`
documentation for export This commit was sponsored by Ole-Morten Duesund on Patreon. 2017-08-29 17:25:48 +00:00			`when initially setting it up with [[git-annex-initremote]](1).`

			`Repeated exports are done efficiently, by diffing the old and new tree,`
			`and transferring only the changed files.`

			`Exports can be interrupted and resumed. However, partially uploaded files`
			`will be re-started from the beginning.`

			`# SEE ALSO`

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

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

			`# AUTHOR`

			`Joey Hess <id@joeyh.name>`

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