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

I think this is an interesting proposal.  I find I rarely delve into
the commits because it takes a noticeable effort just to find out what
each represents.  There are plenty of potential downsides, but perhaps
it's worth making the change to see how well it works.  It doesn't
seem like it'd be hard to switch back if we need to.

Carl Eastlund

On Mon, May 17, 2010 at 7:37 AM, Michael Sperber
<sperber at deinprogramm.de> 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