diff options
Diffstat (limited to 'doc/bare_repositories.mdwn')
| -rw-r--r-- | doc/bare_repositories.mdwn | 25 |
1 files changed, 12 insertions, 13 deletions
diff --git a/doc/bare_repositories.mdwn b/doc/bare_repositories.mdwn index e3c82d019..b7ae0b316 100644 --- a/doc/bare_repositories.mdwn +++ b/doc/bare_repositories.mdwn @@ -1,13 +1,13 @@ +**This is still an experimental feature!** Use with caution. + Due to popular demand, git-annex can now be used with bare repositories. So, for example, you can stash a file away in your repos's origin: `git annex move mybigfile --to origin` Of course, for that to work, the bare repository has to be on a system with -[[git-annex-shell]] installed. If "origin" is on gitweb, you still can't -use git-annex to there. - -**This is still an experimental feature!** +[[git-annex-shell]] installed. If "origin" is on GitWeb, you still can't +use git-annex to store stuff there. Known to work ok: @@ -17,16 +17,15 @@ Known to work ok: that is being dropped. * `git annex get` can transfer data from a bare repository. -There are a few caveats to keep in mind: +There are a few caveats to keep in mind when using bare repositories: * `git annex init` can be run in a bare repository, but it cannot store the name you gave the repository in .git-annex/uuid.log (because - the bare repository has no such file to commit to). -* `git annex fromkey` does something pointless in a bare repository. -* `git annex fsck` cannot detect any problems in a bare repository. -* `git annex unused` will think everything stored in a bare repository - is unused. -* `git annex setkey` is a plumbing-level command, and using it manually + the bare repository has no such file to commit to). Instead, it will + tell you a command to run in some non-bare clone of the repository. +* Some subcommands, like `fsck`, `trust`, `unused` and `fromkey`, + cannot be run in a bare repository. Those subcommands will + refuse to do anything. +* `git annex setkey` is a plumbing-level command; using it manually to add content to a bare repository is not recommended, since there - will be no record accessible by other repositories that the content - is stored there. + will be no record that the content is stored there. |