Mercurial notifications

Andrew John Hughes gnu_andrew at
Sat Mar 15 00:10:54 UTC 2008

On 14/03/2008, Roman Kennke <roman at> wrote:
> Hi Mark,
>  > Once the initial flurry of pushes for the jcheck configuration file that
>  > was needed in each and every repository blew past (sorry about that),
>  > we've seen 61 pushes of actual code into the various JDK 7 development
>  > forests.
> Yeah, that is very nice. Finally we can see what is going on.

+1 from me too :)

>  > The forests were initially configured to send push-notification messages
>  > to the primary -dev mailing lists of the appropriate Group(s).  This
>  > seemed like a reasonable starting point, on the assumption that if a
>  > Group has Members who regularly push code into a JDK 7 forest then
>  > they'll want to (and arguably should) be aware of every push into that
>  > forest.
>  > Some have expressed the concern, privately, that this results in people
>  > receiving too many messages in which they're not actually interested.
>  > There are (at least) a couple of ways to deal with this:
>  >
>  >   - People can filter the incoming messages (look for the X-Hg-URL
>  >     header, which points back to the repository for which the
>  >     notification was generated); or
>  >
>  >   - We could create an additional list for each forest and arrange to
>  >     send Mercurial notifications to those lists only.  People could
>  >     then subscribe to those lists, or subscribe to the appropriate
>  >     per-repository RSS feeds (broken at the moment, but to be fixed
>  >     soon), or live in peaceful ignorance.
>  >
>  > So, what do people think?  Should we create separate per-forest lists for
>  > Mercurial notifications, do nothing, or do something else?
> I think it is important to be able to see every commit. I'm not sure if
>  the commit messages should go to the -dev mailinglists though. I for one
>  would subscribe to the RSS feeds published by the repositories, that is
>  perfect for me. I would rather not create more mailinglists, there are
>  already to many of them. I also don't care having the commit messages on
>  the -dev lists. They are easy enough to filter.

I agree with Roman.  With Classpath we've also had separate
discussion, patch and commit lists.  However, that is for the _whole
project_.  It doesn't scale to the OpenJDK multitude of lists so I
think RSS feeds would be a good option, given the messages are
archived anyway in Mercurial itself.  I think the point about the -dev
lists being flooded with commit messages is a pertinent one; it hides
discussion threads and persists in the archive even if painstakingly
filtered by each user.

>  Cheers,
>  /Roman
>  --

Andrew :-)

Document Freedom Day - March 26th

Support Free Java!
Contribute to GNU Classpath and the OpenJDK

PGP Key: 94EFD9D8 (
Fingerprint: F8EF F1EA 401E 2E60 15FA  7927 142C 2591 94EF D9D8

More information about the discuss mailing list