X-Git-Url: https://sipb.mit.edu/gitweb.cgi/ikiwiki.git/blobdiff_plain/7758dbb27980daceb3e6714b6f3f8c32ee354fc7..35f943e6f8d2c7689ea7649053a09aeac9f0c5f3:/doc/todo/git_attribution/discussion.mdwn

diff --git a/doc/todo/git_attribution/discussion.mdwn b/doc/todo/git_attribution/discussion.mdwn
index 45f40e408..21898a1c9 100644
--- a/doc/todo/git_attribution/discussion.mdwn
+++ b/doc/todo/git_attribution/discussion.mdwn
@@ -10,6 +10,7 @@ I've been thinking a bit about the GIT attribution in ikiwiki...
 
 If no email set, I think "$USERNAME" is reasonable... no point in the
 '<>' causing clutter.
+>> **adjustement wrt comments**: leave the '<>' in due to requirements in git
 
 If no username set... then something like '@[IPADDR]' makes sense...
 (not in email brackets).
@@ -42,7 +43,21 @@ Perhaps an OpenID: $OPENID_URL would make sense.  This could help w/
 making sure that no one irrefutably spoofs a post by someone (since w/
 the setup where email and effective username are configurable, there's
 no determination of uniqueness)
+>> **adj re git req**: "$OPENID_URL <>"
 
 [[harningt]]
 
 [[madduck]]: git requires `Name <Email@address>` format, as far as I know.
+
+> Yes, it does:
+> 
+> 	joey@kodama:~/tmp/foo/bar>git commit --author "foo"
+> 	fatal: malformed --author parameter
+> 
+> It seems to be happy with anything of the form "foo <foo>" -- doesn't seem to
+> do any kind of strict checking. Even "http://joey.kitenet.net <>" will be
+> accepted. --[[Joey]]
+>>
+>>Sounds good to me, 
+>>
+>> --[[harningt]]