summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2010-12-29 20:33:55 -0400
committerGravatar Joey Hess <joey@kitenet.net>2010-12-29 20:33:55 -0400
commita91e31cef3598f622dd73e95151f96eeaedba327 (patch)
tree2c9decac843bcef8ab4173435cf64b305b99923c
parent03e579060b11dcca6115426e7a4255a7ded944e2 (diff)
response
-rw-r--r--doc/todo/git_annex_init_:_include_repo_description_and__47__or_UUID_in_commit_message.mdwn7
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/todo/git_annex_init_:_include_repo_description_and__47__or_UUID_in_commit_message.mdwn b/doc/todo/git_annex_init_:_include_repo_description_and__47__or_UUID_in_commit_message.mdwn
index 9802738d1..9ca61bff5 100644
--- a/doc/todo/git_annex_init_:_include_repo_description_and__47__or_UUID_in_commit_message.mdwn
+++ b/doc/todo/git_annex_init_:_include_repo_description_and__47__or_UUID_in_commit_message.mdwn
@@ -2,3 +2,10 @@ Would help alot when having to add large(ish) amounts of remotes.
Maybe detect this kind of commit message and ask user whether to automatically add them? See [[auto_remotes]]:
> Question: When should git-annex update the remote.log? (If not just on init.) Whenever it reads in a repo's remotes?
+
+----
+
+I'm not sure that the above suggestion is going down a path that really
+makes sense. If you want a list of repository UUIDs and descriptions,
+it's there in machine-usable form in `.git-annex/uuid.log`, there is no
+need to try to pull this info out of git commit messages. --[[Joey]]