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 21898a1c9d270015f623230265f4bef27c8828e0..42cc8449efda7694cf3709dc2a6b115af8453246 100644 (file)
--- a/doc/todo/git_attribution/discussion.mdwn
+++ b/doc/todo/git_attribution/discussion.mdwn
@@ -15,6 +15,8 @@ If no email set, I think "$USERNAME" is reasonable... no point in the
 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.


@@ -51,8 +53,8 @@ no determination of uniqueness)
 
 > Yes, it does:
 > 
 
 > 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
 > 
 > 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