new commits to Kallithea should be sent to the mailing list

Mads Kiilerich mads at
Tue Feb 3 19:51:17 EST 2015

On 02/03/2015 09:51 PM, Thomas De Schampheleire wrote:
> Hi,
> On Sun, Jan 25, 2015 at 5:49 AM, Sean Farley
> <sean.michael.farley at> wrote:
>> Thomas De Schampheleire writes:
>>> Hi,
>>> Currently, new commits on the Kallithea project silently end up in
>>> Bitbucket. In order for users to become aware of such changes and to
>>> create an active community, I believe a mail notification of these
>>> commits should be sent to the mailing list.
>>> I would prefer one mail per commit, but an alternate style is how
>>> Mercurial does it: one mail per bunch of commits.
>>> What do you think?
>> That's a great idea. Andrew, what do you think? Could you set this up on
>> the server?
> I now see commit mails from Our Own Kallithea, but nothing from Bitbucket.
>  From Bitbucket, the only mails currently sent are those for new
> issues. But there are no mails for comments on an existing issue, nor
> are there mails for (new / updated / commented) pull requests.
> Could this be handled too?

You should be able to opt in to follow Kallithea on Bitbucket but it 
does not seem like they have a way to forward it to a mailing list.

Please let me know if you are familiar with Bitbucket and know how it 
can be done.

The best solution would be to implement functionality so our own 
Kallithea could aggregate pull requests from bitbucket and personal 
Kallithea and hgweb installations ... and github.


More information about the kallithea-general mailing list