fix up commands that are trouble on bare repos
Most will just abort. init does a basic init and gives a command to run elsewhere to finish it.
This commit is contained in:
parent
b88637fff1
commit
b5b78f26ec
8 changed files with 31 additions and 23 deletions
|
@ -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.
|
||||
|
|
|
@ -54,6 +54,7 @@ files with git.
|
|||
* git-annex prevents accidental data loss by [[tracking copies|copies]]
|
||||
of your files
|
||||
* [[internals]]
|
||||
* [[bare_repositories]]
|
||||
* [[what git annex is not|not]]
|
||||
* git-annex is Free Software, licensed under the [[GPL]].
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue