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. Cheers, Dirkjan
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4