summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2013-11-02 20:48:41 -0400
committerGravatar Joey Hess <joey@kitenet.net>2013-11-02 20:48:41 -0400
commit6fa117bf16fc542e6c1b1d846f1a4a00e7dad7e7 (patch)
treeda0db56394f7b93048ff2ddc745a4366ac4b2a65
parentacbd34b45063323463f439cbdd9e59c7c0c66e6c (diff)
respond
-rw-r--r--doc/todo/Sync_repo_names__63__.mdwn7
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/todo/Sync_repo_names__63__.mdwn b/doc/todo/Sync_repo_names__63__.mdwn
index c4d81b0d8..d3bb59f04 100644
--- a/doc/todo/Sync_repo_names__63__.mdwn
+++ b/doc/todo/Sync_repo_names__63__.mdwn
@@ -1,3 +1,10 @@
It's very confusing to me that the same repo viewed from different client systems can have different names and descriptions. This implies that making changes to a remote repo from one system only affects how that system sees the repo, but it seems to affect how the entire git-annex "pair" or "network of repos" sees it.
I think it would be good if the names and descriptions of repos were synced across clients.
+
+> The descriptions of repositories are synced. (They're stored in git-annex:uuid.log)
+>
+> git allows for the same repository to be referred to using as many different remote names as you want to set up. git-annex inherits this,
+> and I can't see this changing; there are very good reasons for remotes to
+> have this flexability. [[done]]
+> --[[Joey]]