Email notifications for git commits on git.debian.org

[Reinhard Tartler]

On Mon, Feb 3, 2014 at 10:31 AM, Felipe Sateler <fsateler at debian.org> wrote:
> On Mon, Feb 3, 2014 at 12:06 PM, Reinhard Tartler <siretart at gmail.com> wrote:
>> On Mon, Feb 3, 2014 at 8:48 AM, Felipe Sateler <fsateler at debian.org> wrote:
>>> On Sat, Feb 1, 2014 at 1:05 PM, Reinhard Tartler <siretart at gmail.com> wrote:
>>>> Hi Folks,
>>>>
>>>> I've noticed the following note in the latest developer news regarding
>>>> our commit messages. I know that we have been using our own custom
>>>> post-receive-email hook, and I wonder if now wouldn't be a good time
>>>> to switch to this multimailhook script?
>>>>
>>>> While we are at it, it seems that this multimail hook makes it easy to
>>>> also send VCS notices to KGB (i.e., IRC announcements) and to the PTS.
>>>> I'd like to enable all of them, but first wanted to check with you
>>>> what to look out for. I've again forgot what exact problems our
>>>> post-commit hook fixed.
>>>
>>> I remember I changed the commit script to set the alioth username of
>>> the pusher in the From line, which I believe is then used to
>>> automoderate the commit list.
>>
>> I strongly believe that there we can whitelist the sending hosts as
>> well on the -commits mailing list. If you don't mind, I'd like to
>> test-switch one package to multimailhook, and see if the mails get
>> moderated. If yes, then I'll adjust the sender filters to auto-accept
>> them.
>>
>> sounds good?
>
> Sounds good to me.
>
>
> I have another question, though: what happens with the new workflow of
> merging with the upstream git tag? I think it was you that tweaked the
> script to limit it to max 10 emails?

Yes, that was me. That's two points for us to watch out for.

Thanks for the reminder.

-- 
regards,
    Reinhard