[plt-dev] One e-mail per commit?

That would work fine for me, as long as the change happens only after
Racket is out.

At Mon, 17 May 2010 14:37:37 +0200, Michael Sperber wrote:
> 
> Eli and I have had a private conversation on this for a while - he has
> asked me to make my thoughts public: Currently, the per-push
> notification e-mails are pretty useless to me: 
> 
> - The subject line has zero useful information (for me at least).
> 
> - The granularity of the e-mails may or may not have anything to do with
>   the granularity of development.
> 
> - Ergo I have to download every e-mail to get useful information (my
>   folder lives on IMAP), which is often not even technically practical
>   when I'm travelling, for instance.  Even when I'm fully online, it
>   takes too long to go over the week's commits this way, compared to the
>   old way of doing things with Subversion - the result is that I don't
>   read the commit e-mails anymore.
> 
> So I'd like to propose sending one e-mail per commit instead, where the
> Subject line carries the first line of the commit message.  (We've been
> doing things this way with Scheme 48 and XEmacs, FWIW - works
> wonderfully.)  Possibly, it makes sense to avoid sending e-mails on
> merge commits, but that's only a bonus.  Eli says the ordering may get
> screwed up - not a problem for me.
> 
> -- 
> Cheers =8-} Mike
> Friede, Völkerverständigung und überhaupt blabla
> _________________________________________________
>   For list-related administrative tasks:
>   http://list.cs.brown.edu/mailman/listinfo/plt-dev