"Justin Erenkrantz" <justin@erenkrantz.com> writes:
> For example, I'm telling it to send the commit as me and it's
> configured to send the commit emails to myself and a bunch of
> colleagues. One of those colleagues (call him John) is on vacation
> and set up vacation. Now, if 'vacation' has already informed me that
> John is away, it won't notify me again. However, if 'vacation' hasn't
> done that yet, it'll send me an email that John is gone. That's good.
> I now know that John won't be reviewing my commit. This is ideal for
> small groups which don't justify the overhead of a mailing list.
>
> Now, if you really want bulk precedence, you should just set up a list
> and point the mailer at it - most list managers will add the
> precedence header by default. But, if you send it to a bunch of
> people directly (sans list), the intention (to me) is that you want to
> know if they won't read that commit message. In either of those
> 'normal' cases, mailer shouldn't add the header. Note that some
> mailing lists are configured to reject emails if the Precedence: Bulk
> header is already set in an attempt to limit spam - so doing so might
> cause those commits to be rejected. -- justin
*nod* I'll buy that. And the second paragraph describes a better
solution than setting this as a default in mailer.py.
Thanks for taking the time to write it up,
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Sep 18 19:29:28 2006