summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar praet <praet@web>2010-12-30 00:01:02 +0000
committerGravatar admin <admin@branchable.com>2010-12-30 00:01:02 +0000
commit80bad5c43507d1a3c79d473287a18b041cfd1ed1 (patch)
tree62bb02beb37b63f912208dc0a6e4c3881b7fc098
parent88edf83b5c0a0be2b7776dcc6a0d16676a716d8a (diff)
-rw-r--r--doc/todo/git_annex_init_:_include_repo_description_and__47__or_UUID_in_commit_message.mdwn4
1 files changed, 4 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
new file mode 100644
index 000000000..9802738d1
--- /dev/null
+++ b/doc/todo/git_annex_init_:_include_repo_description_and__47__or_UUID_in_commit_message.mdwn
@@ -0,0 +1,4 @@
+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?