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

2005-10-04 Thread Bill Wohler
Sylvain Beucler <[EMAIL PROTECTED]> writes:

> I setup the [MH-E loginfo messages] (no alias).
>
> There should not be spam issues.

Indeed. I just made a small test and it looks great! Thanks.

-- 
Bill Wohler <[EMAIL PROTECTED]>  http://www.newt.com/wohler/  GnuPG ID:610BD9AD
Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian!
If you're passed on the right, you're in the wrong lane.



___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel


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

2005-10-04 Thread Sylvain Beucler
On Mon, Oct 03, 2005 at 04:14:50PM -0700, Bill Wohler wrote:
> Sylvain Beucler <[EMAIL PROTECTED]> wrote:
> > On Fri, Sep 30, 2005 at 03:49:08PM -0700, Bill Wohler wrote:
> > > Sylvain Beucler <[EMAIL PROTECTED]> wrote:
> > > 
> > > > 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).
> > > 
> > > It's time to proceed with this. But first, a couple of quick questions.
> > > 
> > > I have not been able to find (your version of) the log_accum.pl script
> > > to confirm, but the following email implies that we might be able to say
> > > -m emacs-commit -m mh-e-devel on the command line:
> > > 
> > >   http://lists.gnu.org/archive/html/emacs-devel/2001-11/msg01079.html
> > 
> > Check
> > http://savannah.gnu.org/cgi-bin/viewcvs/administration/administration/infra/commit_prep-log_accum/log_accum.pl?rev=1.4&content-type=text/vnd.viewcvs-markup
> > 
> > Apparently it should work there as well, my bad.
> > 
> > > Then there's the question of the -D option as well.
> > 
> > I don't think all combinations will be possible. Activating the diffs
> > globally for all lists should work.
> > 
> > > Also, is there an option to generate unified diffs instead of context
> > > diffs? With large hunks, it's impossible to compare the changes in
> > > context diffs.
> > 
> > Yes.
> 
> Sylvain,
> 
> Thanks for the pointer to the modified script. If I'm reading it
> correctly, I think that the MH-E developers would be happy (the log
> message and unified diffs for every file in the check-in combined within
> a single message) with a loginfo entry of:
> 
>   ^emacs/lisp/mh-e /bin/log_accum -T emacs -C -m [EMAIL PROTECTED] -m 
> emacs-commit@gnu.org -D -u -r "" -s %{sVv}
> 
> However, if you're correct in that your spam filter will deny this, then
> it should be changed to:
> 
>   ^emacs/lisp/mh-e /bin/log_accum -T emacs -C -m [EMAIL PROTECTED] -D -u -r 
> "" -s %{sVv}
> 
> and an mh-e-commit alias on fencepost should be created that contains
> [EMAIL PROTECTED] and [EMAIL PROTECTED]
> 
> Finally, if the emacs-commit community does not like getting the MH-E
> diffs (unified ones at that) in the same message as the log, then
> emacs-commit should be removed from the mailing list and interested
> individuals should subscribe (assuming that the mailing list is set up
> with mailman and rather than in /etc/aliases).
> 
> Can you makes these changes for me please? If so, please let me know
> when I can test this. Thanks!

I setup the first solution (no alias).

There should not be spam issues.

-- 
Sylvain


___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel


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

2005-10-03 Thread Bill Wohler
Sylvain Beucler <[EMAIL PROTECTED]> wrote:

> On Fri, Sep 30, 2005 at 03:49:08PM -0700, Bill Wohler wrote:
> > Sylvain Beucler <[EMAIL PROTECTED]> wrote:
> > 
> > > 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).
> > 
> > It's time to proceed with this. But first, a couple of quick questions.
> > 
> > I have not been able to find (your version of) the log_accum.pl script
> > to confirm, but the following email implies that we might be able to say
> > -m emacs-commit -m mh-e-devel on the command line:
> > 
> >   http://lists.gnu.org/archive/html/emacs-devel/2001-11/msg01079.html
> 
> Check
> http://savannah.gnu.org/cgi-bin/viewcvs/administration/administration/infra/commit_prep-log_accum/log_accum.pl?rev=1.4&content-type=text/vnd.viewcvs-markup
> 
> Apparently it should work there as well, my bad.
> 
> > Then there's the question of the -D option as well.
> 
> I don't think all combinations will be possible. Activating the diffs
> globally for all lists should work.
> 
> > Also, is there an option to generate unified diffs instead of context
> > diffs? With large hunks, it's impossible to compare the changes in
> > context diffs.
> 
> Yes.

Sylvain,

Thanks for the pointer to the modified script. If I'm reading it
correctly, I think that the MH-E developers would be happy (the log
message and unified diffs for every file in the check-in combined within
a single message) with a loginfo entry of:

  ^emacs/lisp/mh-e /bin/log_accum -T emacs -C -m [EMAIL PROTECTED] -m 
emacs-commit@gnu.org -D -u -r "" -s %{sVv}

However, if you're correct in that your spam filter will deny this, then
it should be changed to:

  ^emacs/lisp/mh-e /bin/log_accum -T emacs -C -m [EMAIL PROTECTED] -D -u -r "" 
-s %{sVv}

and an mh-e-commit alias on fencepost should be created that contains
[EMAIL PROTECTED] and [EMAIL PROTECTED]

Finally, if the emacs-commit community does not like getting the MH-E
diffs (unified ones at that) in the same message as the log, then
emacs-commit should be removed from the mailing list and interested
individuals should subscribe (assuming that the mailing list is set up
with mailman and rather than in /etc/aliases).

Can you makes these changes for me please? If so, please let me know
when I can test this. Thanks!

-- 
Bill Wohler <[EMAIL PROTECTED]>  http://www.newt.com/wohler/  GnuPG ID:610BD9AD
Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian!
If you're passed on the right, you're in the wrong lane.


___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel


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

2005-10-01 Thread Sylvain Beucler
On Fri, Sep 30, 2005 at 03:49:08PM -0700, Bill Wohler wrote:
> Sylvain Beucler <[EMAIL PROTECTED]> wrote:
> 
> > On Sat, Jun 04, 2005 at 09:13:37AM -0700, Bill Wohler wrote:
> > > Miles Bader <[EMAIL PROTECTED]> wrote:
> > > 
> > > > On 6/4/05, Sylvain Beucler <[EMAIL PROTECTED]> 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,
> 
> It's time to proceed with this. But first, a couple of quick questions.
> 
> I have not been able to find (your version of) the log_accum.pl script
> to confirm, but the following email implies that we might be able to say
> -m emacs-commit -m mh-e-devel on the command line:
> 
>   http://lists.gnu.org/archive/html/emacs-devel/2001-11/msg01079.html

Check
http://savannah.gnu.org/cgi-bin/viewcvs/administration/administration/infra/commit_prep-log_accum/log_accum.pl?rev=1.4&content-type=text/vnd.viewcvs-markup

Apparently it should work there as well, my bad.

> Then there's the question of the -D option as well.

I don't think all combinations will be possible. Activating the diffs
globally for all lists should work.

> Also, is there an option to generate unified diffs instead of context
> diffs? With large hunks, it's impossible to compare the changes in
> context diffs.

Yes.

-- 
Sylvain


___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel


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

2005-09-30 Thread Bill Wohler
Sylvain Beucler <[EMAIL PROTECTED]> wrote:

> On Sat, Jun 04, 2005 at 09:13:37AM -0700, Bill Wohler wrote:
> > Miles Bader <[EMAIL PROTECTED]> wrote:
> > 
> > > On 6/4/05, Sylvain Beucler <[EMAIL PROTECTED]> 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,

It's time to proceed with this. But first, a couple of quick questions.

I have not been able to find (your version of) the log_accum.pl script
to confirm, but the following email implies that we might be able to say
-m emacs-commit -m mh-e-devel on the command line:

  http://lists.gnu.org/archive/html/emacs-devel/2001-11/msg01079.html

Then there's the question of the -D option as well.

Also, is there an option to generate unified diffs instead of context
diffs? With large hunks, it's impossible to compare the changes in
context diffs.

-- 
Bill Wohler <[EMAIL PROTECTED]>  http://www.newt.com/wohler/  GnuPG ID:610BD9AD
Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian!
If you're passed on the right, you're in the wrong lane.


___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel


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

2005-06-04 Thread Richard Stallman
It should be possible for someone to write a filter to read
the diffs that are already being mailed out, and discard
all but those that pertain to the lisp/mh-e directory.


___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel


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

2005-06-04 Thread Sylvain Beucler
On Sat, Jun 04, 2005 at 09:13:37AM -0700, Bill Wohler wrote:
> Miles Bader <[EMAIL PROTECTED]> wrote:
> 
> > On 6/4/05, Sylvain Beucler <[EMAIL PROTECTED]> 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


___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel


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

2005-06-04 Thread Bill Wohler
Miles Bader <[EMAIL PROTECTED]> wrote:

> On 6/4/05, Sylvain Beucler <[EMAIL PROTECTED]> 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?

-- 
Bill Wohler <[EMAIL PROTECTED]>  http://www.newt.com/wohler/  GnuPG ID:610BD9AD
Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian!
If you're passed on the right, you're in the wrong lane.


___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel


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

2005-06-04 Thread Miles Bader
On 6/4/05, Sylvain Beucler <[EMAIL PROTECTED]> 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.

-Miles
-- 
Do not taunt Happy Fun Ball.


___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel


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

2005-06-04 Thread Sylvain Beucler
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).

Currently we do not have to resources to work on this script to bypass
CVS's limitations, but the source code is freely available at
administration/administration/infra/commit_prep-log_accum/ in the
administration project repository at Savannah.

-- 
Sylvain

On Fri, Jun 03, 2005 at 04:25:14PM -0700, Bill Wohler wrote:
> Richard Stallman <[EMAIL PROTECTED]> wrote:
> 
> > > If this switch comes to pass, would the Emacs developers mind if 
> > I added
> > > the following line to CVSROOT/loginfo?
> > > 
> > >  lisp/mh-e $CVSROOT/CVSROOT/syncmail -u %{sVv} [EMAIL PROTECTED]
> > > 
> > > Would you please explain what this would do?  I don't understand,
> > > but I can't say yes until I understand.
> > 
> > This loginfo entry calls syncmail on each check-in for the lisp/mh-e
> > directory. The syncmail script, when run in the CVS loginfo context will
> > send a diff of each check-in to the given mailing list (mh-e-devel).
> > 
> > Ok with me.
> 
> Thanks.
> 
> -- 
> Bill Wohler <[EMAIL PROTECTED]>  http://www.newt.com/wohler/  GnuPG 
> ID:610BD9AD
> Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian!
> If you're passed on the right, you're in the wrong lane.


___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel