emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Savannah-help-public] Re: The MH-E repository


From: Sylvain Beucler
Subject: Re: [Savannah-help-public] Re: The MH-E repository
Date: Sat, 4 Jun 2005 18:52:20 +0200
User-agent: Mutt/1.5.6+20040907i

On Sat, Jun 04, 2005 at 09:13:37AM -0700, Bill Wohler wrote:
> Miles Bader <address@hidden> wrote:
> 
> > On 6/4/05, Sylvain Beucler <address@hidden> wrote:
> > > Considering that you want lisp/mh-e to notify both mh-e-devel and
> > > emacs-commit, this is currently not possible in the current setup,
> > > mainly because CVS's loginfo only matches one configuration file line,
> > > and each line call our notification script that only accept 1 e-mail
> > > address per kind of notifications (diff / nodiff).
> > 
> > As a work-around, you could have it send to an alias (I mean one in
> > /etc/aliases or equivalent) which in turn just forwards to both lists.
> 
> That's true. What might be a better alternative is that I could (and
> probably should) set up an mh-e-commits mailing list. I'd add
> emacs-commits to that list.
> 
> At first I thought that the Emacs folks would not really be interested
> in seeing the MH-E commits, but perhaps that would not be the case.
> 
> However, if the Emacs maintainers don't even *want* to have an
> emacs-commits mailing list, then this is a moot point. Do they?

The FSF set up an anti-spam rule that block mail "from AND to mailing
lists" :/

However I/Miles/... should be able to setup an alias at fencepost :)
Indeed.

Please tell me what you decide (whether commits should go to both
mailing lists or only mh-e-devel).

-- 
Sylvain




reply via email to

[Prev in Thread] Current Thread [Next in Thread]