X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/562e24d695a88b0da851de44952d73568a62712e..e767f18867bbddb252bd53589676f29dfc75837e:/doc/todo/git_attribution/discussion.mdwn?ds=sidebyside

diff --git a/doc/todo/git_attribution/discussion.mdwn b/doc/todo/git_attribution/discussion.mdwn
index d7796c017..42cc8449e 100644
--- a/doc/todo/git_attribution/discussion.mdwn
+++ b/doc/todo/git_attribution/discussion.mdwn
@@ -10,10 +10,13 @@ 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).
 
+> Why not put it in email brackets? --[[Joey]]
+
 In the case of OpenID login.. I think that's a special case...  I don't
 think attempting to munge something meaningful out of the OpenID makes
 sense... but I think some massaging might need to be done.
@@ -42,6 +45,7 @@ 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]]
 
@@ -49,9 +53,13 @@ no determination of uniqueness)
 
 > Yes, it does:
 > 
-> 	joey@kodama:~/tmp/foo/bar>git commit --author "foo"
-> 	fatal: malformed --author parameter
+>     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]]