diff options
author | Joey Hess <joey@kitenet.net> | 2011-06-22 18:32:41 -0400 |
---|---|---|
committer | Joey Hess <joey@kitenet.net> | 2011-06-22 18:32:41 -0400 |
commit | 80302d0b46c5d45df1cf290796e0e27d9264ece8 (patch) | |
tree | c97312a531f5cf2ef514ddb5224395b614eb2b25 /doc/bare_repositories.mdwn | |
parent | 944c51ba26efc39416c5f148b6ec36151dc7f42e (diff) |
improve bare repo handing
Many more commands can work in bare repos now, thanks to the git-annex
branch.
Diffstat (limited to 'doc/bare_repositories.mdwn')
-rw-r--r-- | doc/bare_repositories.mdwn | 9 |
1 files changed, 3 insertions, 6 deletions
diff --git a/doc/bare_repositories.mdwn b/doc/bare_repositories.mdwn index 5cbad5c2d..c5663d84c 100644 --- a/doc/bare_repositories.mdwn +++ b/doc/bare_repositories.mdwn @@ -14,12 +14,9 @@ Known to work ok: * `git annex drop` can check that a bare repository has a copy of data that is being dropped. * `git annex get` can transfer data from a bare repository. +* Most other stuff (ie, init, describe, trust, etc.) There are a few caveats to keep in mind when using bare repositories: -* 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 that the content is stored there. +* A few subcommands, like `unused` cannot be run in a bare repository. + Those subcommands will refuse to do anything. |