[CF-metadata] Trac forwarding to mailing list

Dave Allured - NOAA Affiliate dave.allured at noaa.gov
Wed Oct 25 14:33:15 MDT 2017


A couple people confirmed to me that Trac forwarding is currently working
as intended.  Thanks Jeff and Karl.

The tricky thing is that Trac messages bypass the Mailman process, so they
don't go into the Mailman archive, or receive the Mailman footer lines.

Sorry for the extra noise, but I am glad to get this confirmed.


On Wed, Oct 25, 2017 at 1:11 PM, Dave Allured - NOAA Affiliate <
dave.allured at noaa.gov> wrote:

> Jonathan,
> Thanks for mentioning this.  It is difficult for the ticket creator to
> confirm broadcast of a new ticket message.  I am not sure whether the new
> ticket confirmation that I received was broadcast or a private reply, but I
> notice that the Mailman list trailer is absent.  This indicates private
> reply, but it could also be Gmail's duplication suppression playing tricks.
> As a test, did you receive the original Trac new ticket messages for
> either #166 (Oct 1) or #167 (Oct 19)?  They would have the ticket number in
> the subject line.
> The Mailman archive contains no trace of recent Trac messages, either new
> tickets or added comments.  This suggests there is no forwarding, but there
> could be another explanation.  Meanwhile, some of us conclude we should
> independently send our own new ticket announcements.  It would be nice to
> get clarification of how Trac forwarding currently works.
> --Dave
> From: Jonathan Gregory <j.m.gregory at reading.ac.uk>
> Date: Wed, Oct 25, 2017 at 6:40 AM
> Subject: [CF-metadata] Use of valid_range etc. to indicate unsigned
> integers
> To: cf-metadata at cgd.ucar.edu
> Dear Dave
> > I did not realize that new tickets are
> > not automatically sent to the CF general mailing list.
> They *should* be sent to everyone, if the system is working as intended.
> Best wishes
> Jonathan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.cgd.ucar.edu/pipermail/cf-metadata/attachments/20171025/cb968322/attachment-0001.html>

More information about the CF-metadata mailing list