diff options
author | 2013-03-18 20:07:59 -0400 | |
---|---|---|
committer | 2013-03-18 20:07:59 -0400 | |
commit | c76bcdc47e0d4a48b9b9cc91718255e89c535d05 (patch) | |
tree | 2aed28a0de95f8b8b2d0c2d440c2917b884ea2f3 /doc/bugs/Renamed_special_remote_cannot_be_reactivated_by_the_webapp.mdwn | |
parent | a46424e78b1cd98f87ee62a49b63acff7e6d890c (diff) |
bug triaging and tagging
Diffstat (limited to 'doc/bugs/Renamed_special_remote_cannot_be_reactivated_by_the_webapp.mdwn')
-rw-r--r-- | doc/bugs/Renamed_special_remote_cannot_be_reactivated_by_the_webapp.mdwn | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/bugs/Renamed_special_remote_cannot_be_reactivated_by_the_webapp.mdwn b/doc/bugs/Renamed_special_remote_cannot_be_reactivated_by_the_webapp.mdwn index 605027f28..ccf6ef1ca 100644 --- a/doc/bugs/Renamed_special_remote_cannot_be_reactivated_by_the_webapp.mdwn +++ b/doc/bugs/Renamed_special_remote_cannot_be_reactivated_by_the_webapp.mdwn @@ -26,3 +26,5 @@ Workaround: * rename `metaarray` to `ma` again using the webapp Perhaps the renaming of the remote not surviving clones is unavoidable, but the webapp should be able to cope with the situation. Thanks. + +[[!tag /design/assistant]] |