From a91e31cef3598f622dd73e95151f96eeaedba327 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 29 Dec 2010 20:33:55 -0400 Subject: [PATCH] response --- ...epo_description_and__47__or_UUID_in_commit_message.mdwn | 7 +++++++ 1 file changed, 7 insertions(+) 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 9802738d12..9ca61bff55 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]]