Are we getting trunk commit e-mails?

This would seem to be an essential part of our development process.

Does anyone know how this process works?

On 2 February 2012 04:18, Chris Muller <[hidden email]> wrote:
> This would seem to be an essential part of our development process.
>
> Does anyone know how this process works?

The last one I've seen was on 31 Jan (2 days ago):

Bert Freudenberg uploaded a new version of Monticello to project The Trunk:
http://source.squeak.org/trunk/Monticello-bf.493.mcz

==================== Summary ====================

Name: Monticello-bf.493
Author: bf
Time: 31 January 2012, 11:37:31.927 am
UUID: bab611f2-407f-4a06-9168-5cc5180db0fc
Ancestors: Monticello-cmm.492

use more sensible ordering when showing version history

=============== Diff against Monticello-cmm.492 ===============

On 02.02.2012, at 03:08, Frank Shearar wrote:

> On 2 February 2012 04:18, Chris Muller <[hidden email]> wrote:
>> This would seem to be an essential part of our development process.
>>
>> Does anyone know how this process works?

Any squeaksource project can be configured

According to the log, that was indeed the last trunk update:

2012-01-31T19:37:37.644+00:00 PUT /trunk/Monticello-bf.493.mcz (bf)
2012-01-31T19:37:40.711+00:00 STORED trunk/Monticello-bf.493.mcz
2012-01-31T20:34:52.032+00:00 PUT /VMMaker/CMakeVMMaker-EstebanLorenzano.148.mcz (EL)
2012-01-31T20:34:52.508+00:00 STORED VMMaker/CMakeVMMaker-EstebanLorenzano.148.mcz
2012-02-02T01:52:51.634+00:00 PUT /VMMaker/VMMaker.oscog-eem.142.mcz (eem)
2012-02-02T01:52:54.909+00:00 STORED VMMaker/VMMaker.oscog-eem.142.mcz

- Bert -

>>> Does anyone know how this process works?
>
> Any squeaksource project can be configured

Ah, forgot about that.  Thanks.