BTW, I love that github gives you the comment in the subject for the distributed email.

-Steve



----- Original Message -----
> From:"noreply at github.com" <noreply at github.com>
> To:phobos at puremagic.com
> Cc:
> Sent:Monday, January 24, 2011 8:50 PM
> Subject:[phobos] [D-Programming-Language/phobos] fc1155: detab, tolf
> 
> Branch: refs/heads/master
> Home:  https://github.com/D-Programming-Language/phobos
> 
> Commit: fc1155d8236ca01fcbf9db50670ce0dea3245163
> 
> https://github.com/D-Programming-Language/phobos/commit/fc1155d8236ca01fcbf9db50670ce0dea3245163
> Author: Walter Bright <walter at walterbright.com>
> Date:   2011-01-24 (Mon, 24 Jan 2011)
> 
> Changed paths:
>   M std/mathspecial.d
> 
> Log Message:
> -----------
> detab, tolf
> 
> 
> _______________________________________________
> phobos mailing list
> phobos at puremagic.com
> http://lists.puremagic.com/mailman/listinfo/phobos

On Tue, 2011-01-25 at 05:24 -0800, Steve Schveighoffer wrote:
> BTW, I love that github gives you the comment in the subject for the distributed email.

I agree.  Here's a related excerpt from the git-commit man page:

"Though not required, it?s a good idea to begin the commit message with a single short (less than 50 character) line summarizing the change, followed by a blank line and then a more thorough description. Tools that turn commits into email, for example, use the first line on the Subject: line and the rest of the commit in the body."

It's probably a good idea to try to follow this advice.

-Lars