From b88637fff10d4d845404882e4ec95cfc071dcac0 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 3 Mar 2011 16:22:53 -0400 Subject: prevent trust commands from trying to do things in a bare repo Since they need to stage changes, they would actually, if allowed to run, succeed, but wipe out existing trust.log content. --- doc/bare_repositories.mdwn | 3 --- 1 file changed, 3 deletions(-) (limited to 'doc/bare_repositories.mdwn') diff --git a/doc/bare_repositories.mdwn b/doc/bare_repositories.mdwn index f08cf605d..e3c82d019 100644 --- a/doc/bare_repositories.mdwn +++ b/doc/bare_repositories.mdwn @@ -19,12 +19,9 @@ Known to work ok: There are a few caveats to keep in mind: -* Using non-local bare repositories is not tested and probably broken. * `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 trust` cannot be used in a bare repository, and currently - does something pointless. Same for `untrust` and `semitrust`. * `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 -- cgit v1.2.3