summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar https://www.google.com/accounts/o8/id?id=AItOawmGxww5ON3nilm7moGQCWJPnMEdRwNvb7U <Chris@web>2013-10-29 21:58:05 +0000
committerGravatar admin <admin@branchable.com>2013-10-29 21:58:05 +0000
commit894a5bdca10573aa238c3977704b88be906f275b (patch)
treee59d8f1b2ece606c65e195a51cd48638d5d89511
parent568bfdfa7972e5387b0fa65fdc780e8cd9de97cf (diff)
-rw-r--r--doc/bugs/git_annex_dead_does_not_work_as_expected_when_multiple_repos_exist_with_the_same_name___40__notably_including_dead_ones__41__.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/bugs/git_annex_dead_does_not_work_as_expected_when_multiple_repos_exist_with_the_same_name___40__notably_including_dead_ones__41__.mdwn b/doc/bugs/git_annex_dead_does_not_work_as_expected_when_multiple_repos_exist_with_the_same_name___40__notably_including_dead_ones__41__.mdwn
index cbf79ffaf..7e26f63df 100644
--- a/doc/bugs/git_annex_dead_does_not_work_as_expected_when_multiple_repos_exist_with_the_same_name___40__notably_including_dead_ones__41__.mdwn
+++ b/doc/bugs/git_annex_dead_does_not_work_as_expected_when_multiple_repos_exist_with_the_same_name___40__notably_including_dead_ones__41__.mdwn
@@ -2,7 +2,7 @@
Creating two repos with the same name causes git annex dead to randomly choose one. This is reasonable except that it can choose to mark an already dead remote dead (as long as it shares the name), causing it to actually do nothing.
-I think preferring to mark live repos dead and printing a warning when multiple repos could have been chosen would be a good solution.
+I think preferring to mark live repos dead and printing a warning when multiple repos could have been chosen (or if the repo is already marked dead) would be a good solution.
### What steps will reproduce the problem?