diff options
author | 2016-02-19 15:18:02 -0400 | |
---|---|---|
committer | 2016-02-19 15:18:02 -0400 | |
commit | 3b92ac1b6db758665445b8de352afde8f6bd5086 (patch) | |
tree | 008c511d6eea4fdcbdd3c7db1557405b8c531f5c | |
parent | ac44d32ce0d67b2eb7f1e5ae814affa8399a682d (diff) |
close
-rw-r--r-- | doc/bugs/after_git_annex_add_and_commit__44___git_annex_fsck_fails:_no_known_copies.mdwn | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/bugs/after_git_annex_add_and_commit__44___git_annex_fsck_fails:_no_known_copies.mdwn b/doc/bugs/after_git_annex_add_and_commit__44___git_annex_fsck_fails:_no_known_copies.mdwn index 9cc0c031c..0d7804a43 100644 --- a/doc/bugs/after_git_annex_add_and_commit__44___git_annex_fsck_fails:_no_known_copies.mdwn +++ b/doc/bugs/after_git_annex_add_and_commit__44___git_annex_fsck_fails:_no_known_copies.mdwn @@ -9,3 +9,8 @@ Unfortunately, I am not able to reproduce the problem on a toy-example repositor I use git v1.9.1 on Ubuntu 14.04 LTS, and git-annex version: 5.20150406-gb2814bc OK, in all honesty, I did a 'git annex sync' between the 'add' and the 'commit' above. But I synced with a clone of the repository that I keep on an external drive, which is less updated than my laptop. It is less updated because I always add content on my laptop and then sync/get from the external disk. So the sync did no harm, apparently. + +> Since this seems to be only a problem with messaging about accidentially +> marked dead repositories, I've made fsck mention when a file is only +> located in a dead repo, and I've made info tell when it's run in a +> supposedly-dead repo. [[done]] --[[Joey]] |