diff options
| author |  RaspberryPie <RaspberryPie@web> | 2013-10-28 18:31:21 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2013-10-28 18:31:21 +0000 |
| commit | 4878df12bf758e351bc3c35dab5cf265aa88853d (patch) | |
| tree | 0c999447ab458e6d5adce7341f42909306dcecda | |
| parent | 8fdc1813592d4ea72cd22c438b0357b9968fd867 (diff) | |
Added a comment
| -rw-r--r-- | doc/forum/known_and_local_annex_keys/comment_2_68f20c881eafe986694bde10571cf1c0._comment | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/forum/known_and_local_annex_keys/comment_2_68f20c881eafe986694bde10571cf1c0._comment b/doc/forum/known_and_local_annex_keys/comment_2_68f20c881eafe986694bde10571cf1c0._comment new file mode 100644 index 000000000..944ec9caf --- /dev/null +++ b/doc/forum/known_and_local_annex_keys/comment_2_68f20c881eafe986694bde10571cf1c0._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="RaspberryPie" + ip="77.247.181.165" + subject="comment 2" + date="2013-10-28T18:31:21Z" + content=""" +I don't think I'm stressing too much. Rather, I'm inquiring about why git-annex is giving me wrong (or at least unclear) output that makes me worry about losing data. I plan to trust git-annex with a lot of important files, and in order to do that I want to make sure it's trustworthy. And that's where the inaccurate key numbers get in the way. + +So why do the local and known numbers diverge anyway? Would you consider adjusting the status output to be more accurate, or at least less confusing? I just want to be able to check that every single file in the repo is being backed up. +"""]] |