diff options
| author |  http://christian.amsuess.com/chrysn <chrysn@web> | 2010-12-20 13:20:00 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2010-12-20 13:20:00 +0000 |
| commit | d0cba98c5b1297b2bebbf2d75eb4960e3ac07779 (patch) | |
| tree | 9aa645e4aa45ec5fa1a291c2f601e7507b20b001 | |
| parent | ada2a925195152cde1961eee4b3529f72b51aef8 (diff) | |
misleading error message on empty repo
| -rw-r--r-- | doc/bugs/git_annex_unused_failes_on_empty_repository.mdwn | 13 |
1 files changed, 13 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 new file mode 100644 index 000000000..9be98104a --- /dev/null +++ b/doc/bugs/git_annex_unused_failes_on_empty_repository.mdwn @@ -0,0 +1,13 @@ +[[!meta title="`git annex unused` fails on empty repository"]] + +The ``git annex unused`` command fails on a git-annex repository, if there are no objects yet: + + $ git annex unused + unused (checking for unused data...) + git-annex: /tmp/annextest/other_annex/.git/annex/objects: getDirectoryContents: does not exist (No such file or directory) + git-annex: 1 failed + $ + +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). |