The code has now been merged into the standard sender-demunger, and
dev@syncope has been reverted to standard.
Any list should now be able to receive Travis mails.
The only config required is to add 'bui...@travis-ci.org' to the
'allow' subscribers for the list (do not add it as an ordinary
Great, thanks for trying.
On Fri, 9 Aug 2019 at 09:24, Francesco Chicchiriccò wrote:
>
> On 09/08/19 09:58, sebb wrote:
> > Should be set now.
> > I've temporarily added myself as a moderator in case there are issues.
>
> It seems it already worked, cool:
>
>
On 09/08/19 09:58, sebb wrote:
Should be set now.
I've temporarily added myself as a moderator in case there are issues.
It seems it already worked, cool:
https://lists.apache.org/thread.html/b599c5d9c583c6f58de7f51c47fb91903f54928281c2f3a4652bcce2@%3Cdev.syncope.apache.org%3E
Thanks!
On
Should be set now.
I've temporarily added myself as a moderator in case there are issues.
On Fri, 9 Aug 2019 at 08:42, Francesco Chicchiriccò wrote:
>
> On 09/08/19 00:00, sebb wrote:
> > It looks like the Travis-CI reports are not making it to the dev@ list.
> >
> > This is perhaps because each
On 09/08/19 00:00, sebb wrote:
It looks like the Travis-CI reports are not making it to the dev@ list.
This is perhaps because each one has to be moderated, which is a pain.
If so, and the project would like to receive the reports, I am
currently testing a solution which avoids the need to
It looks like the Travis-CI reports are not making it to the dev@ list.
This is perhaps because each one has to be moderated, which is a pain.
If so, and the project would like to receive the reports, I am
currently testing a solution which avoids the need to moderate each
one.
See: