Merge commit 'smcv/master'

[git.ikiwiki.info.git] / doc / todo / git_attribution / discussion.mdwn

diff --git a/doc/todo/git_attribution/discussion.mdwn b/doc/todo/git_attribution/discussion.mdwn
index 74977e0421655ae771240a28990f9ece693dc4ad..42cc8449efda7694cf3709dc2a6b115af8453246 100644 (file)
--- 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.
 
 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).
 
 
 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.
 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,5 +45,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)
 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]]
 
 [[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]]