Hi all,
I've asked ITS to install a git post-commit hook to send an email after commits in the toolchain git repos. It turns out that they prefer to send such email to mailing-lists, to avoid having to maintain the list of recipients themselves, which of course really makes sense.
So far, we already have a cbuild2 mailing-list for commits, which Rob asked to now point to abe instead of cbuild2 repo.
I was thinking about asking a single new mailing-list (eg tcwg-commits) and send commit emails to that list for all ours repos, instead of having a list per repo to which interested team members would have to subscribe.
We currently have the following git repos: abe backflip backport-tools binutils-gdb binutils cbuild2 cortex-malloc cortex-strings cross-build-tools dejagnu dmucs eglibc fakebench gcc-new gcc gdb glibc lavabench newlib release-notes spec2xxx-utils tcwg-sysadmin
Any objection to having such a list? (I do not plan to force subscription of any of you :-)
Christophe.
On 7 December 2014 at 10:13, Christophe Lyon christophe.lyon@linaro.org wrote:
I was thinking about asking a single new mailing-list (eg tcwg-commits) and send commit emails to that list for all ours repos, instead of having a list per repo to which interested team members would have to subscribe.
I think it makes sense. Multiple lists will be harder to maintain, and people can easily filter out messages from repositories they're not interested in.
Filters on mail clients (such as Thunderbird and Sylpheed) and on GMail web interface are powerful enough for that kind of thing.
I, for instance, don't need to be subscribed to any of them, so I will abstain my registration. But once I do, I'll create filters to keep only the things I need.
cheers, --renato
linaro-toolchain@lists.linaro.org