[Python-Dev] notifications form Hg to python-checkins

Tim Delaney timothy.c.delaney at gmail.com
Wed Jul 14 23:21:42 CEST 2010


On 14 July 2010 18:26, Dirkjan Ochtman <dirkjan at ochtman.nl> wrote:

> On Wed, Jul 14, 2010 at 10:15, Georg Brandl <g.brandl at gmx.net> wrote:
> > I also don't think we will see pushes like Tarek's 100+ one very often
> for
> > Python.  Usually changes will be bug fixes, and unless the committer is
> > offline I expect them to be pushed immediately.
>
> Depends. If we do feature branches in separate clones, the merges for
> those can potentially push large numbers of csets at once.
>
> Presumably, we could push some more complexity into the hook, and have
> it send emails per-group for groups of 5 and larger and per-cset for
> smaller groups.
>
> > No, I think we agreed to put the (first line of the) commit message
> there,
> > which I think tells potential reviewers much better if they want to look
> > at that changeset.
>
> Not sure there was actual consensus on that, but I still stand behind
> this point.
>
> If development work was done in named branches, the hook could send one
email per branch that was delivered, and to be safe, one email per changeset
added to a main feature branch.

Tim Delaney
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20100715/b7220601/attachment.html>


More information about the Python-Dev mailing list