summaryrefslogtreecommitdiff
path: root/doc/bugs/git_annex_unused_failes_on_empty_repository.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2010-12-20 14:57:43 -0400
committerGravatar Joey Hess <joey@kitenet.net>2010-12-20 14:57:43 -0400
commitc4a357d5d13e6c2f09ee98ee6ef8b18104e5d167 (patch)
tree44d37ce34184a4cdf30bccddc9104daaf4a8171a /doc/bugs/git_annex_unused_failes_on_empty_repository.mdwn
parentea70873b112c9a1a4471bbd263001975e69e6bdf (diff)
Bugfix to git annex unused in a repository with nothing yet annexed.
Diffstat (limited to 'doc/bugs/git_annex_unused_failes_on_empty_repository.mdwn')
-rw-r--r--doc/bugs/git_annex_unused_failes_on_empty_repository.mdwn2
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/bugs/git_annex_unused_failes_on_empty_repository.mdwn b/doc/bugs/git_annex_unused_failes_on_empty_repository.mdwn
index 9be98104a..05aa69572 100644
--- a/doc/bugs/git_annex_unused_failes_on_empty_repository.mdwn
+++ b/doc/bugs/git_annex_unused_failes_on_empty_repository.mdwn
@@ -11,3 +11,5 @@ The ``git annex unused`` command fails on a git-annex repository, if there are n
This can give a user (especially one that wants to try out simple commands with his newly created repo) the impression that something is wrong, while it is not. I'd expect the program either to show the same message ``git annex unused`` shows when everything is ok (since it is, or should be).
This can be a bug in the ``unused`` subcommand (that fails to accept the absence of an objects directory) or in the ``init`` subcommand (that fails to create it).
+
+> [[fixed|done]] --[[Joey]]