munge to avoid markdown eating email addresses
parent
e96aa16ab9
commit
4f6c544fa8
|
@ -72,7 +72,7 @@ no determination of uniqueness)
|
||||||
> GIT_AUTHOR_EMAIL can also be set.
|
> GIT_AUTHOR_EMAIL can also be set.
|
||||||
>
|
>
|
||||||
> There is one thing yet to be solved, and that is how to tell the
|
> There is one thing yet to be solved, and that is how to tell the
|
||||||
> difference between a web commit by 'Joey Hess <joey@kitenet.net>',
|
> difference between a web commit by 'Joey Hess <joey\@kitenet.net>',
|
||||||
> and a git commit by the same. I think we do want to differentiate these,
|
> and a git commit by the same. I think we do want to differentiate these,
|
||||||
> and the best way to do it seems to be to add a line to the end of the
|
> and the best way to do it seems to be to add a line to the end of the
|
||||||
> commit message. Something like: "\n\nWeb-commit: true"
|
> commit message. Something like: "\n\nWeb-commit: true"
|
||||||
|
@ -94,5 +94,5 @@ no determination of uniqueness)
|
||||||
> * github pushes to twitter ;-)
|
> * github pushes to twitter ;-)
|
||||||
>
|
>
|
||||||
> So while I tried that way at first, I'm now leaning toward encoding the
|
> So while I tried that way at first, I'm now leaning toward encoding the
|
||||||
> username in the email address. Like "user <user@web>", or
|
> username in the email address. Like "user <user\@web>", or
|
||||||
> "joey <http://joey.kitenet.net/@web>".
|
> "joey <http://joey.kitenet.net/\@web>".
|
||||||
|
|
Loading…
Reference in New Issue