* MH-E diffs no longer sent to mh-e-devel
@ 2009-01-12 4:56 Bill Wohler
2009-01-12 8:04 ` [Savannah-help-public] " Sylvain Beucler
0 siblings, 1 reply; 3+ messages in thread
From: Bill Wohler @ 2009-01-12 4:56 UTC (permalink / raw)
To: savannah-hackers; +Cc: emacs-devel
Glenn Morris <rgm@gnu.org> wrote:
> Bill Wohler wrote (on Sat, 10 Jan 2009 at 19:59 -0800):
>
> > You know, I haven't seen the commit messages for your recent changes. Do
> > you know if a CVS loginfo or alias change has occurred recently? Who
> > should I notify about this? I had arranged to have a copy of commit
> > messages for emacs/lisp/mh-e go to mh-e-devel@lists.sourcforge.net.
>
> It used to be that CVS log messages went to emacs-commit, and the
> diffs went to emacs-diffs. Since a few weeks ago, everything goes to
> the diffs list (with the cvs logs as a header). It may be this has
> messed things up. I suggest asking savannah-hackers@gnu.org, with a cc
> to emacs-devel.
Greetings. If what Glenn says is true, could you please reinstate the
configuration that we had set up some time ago so that a copy of the
diffs for MH-E (I think it was just emacs/lisp/mh-e) go to
mh-e-devel@lists.sourceforge.net? Thank you!
--
Bill Wohler <wohler@newt.com> http://www.newt.com/wohler/ GnuPG ID:610BD9AD
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Savannah-help-public] MH-E diffs no longer sent to mh-e-devel
2009-01-12 4:56 MH-E diffs no longer sent to mh-e-devel Bill Wohler
@ 2009-01-12 8:04 ` Sylvain Beucler
2009-01-25 18:46 ` Bill Wohler
0 siblings, 1 reply; 3+ messages in thread
From: Sylvain Beucler @ 2009-01-12 8:04 UTC (permalink / raw)
To: Bill Wohler; +Cc: savannah-hackers, emacs-devel
On Sun, Jan 11, 2009 at 08:56:24PM -0800, Bill Wohler wrote:
> Glenn Morris <rgm@gnu.org> wrote:
>
> > Bill Wohler wrote (on Sat, 10 Jan 2009 at 19:59 -0800):
> >
> > > You know, I haven't seen the commit messages for your recent changes. Do
> > > you know if a CVS loginfo or alias change has occurred recently? Who
> > > should I notify about this? I had arranged to have a copy of commit
> > > messages for emacs/lisp/mh-e go to mh-e-devel@lists.sourcforge.net.
> >
> > It used to be that CVS log messages went to emacs-commit, and the
> > diffs went to emacs-diffs. Since a few weeks ago, everything goes to
> > the diffs list (with the cvs logs as a header). It may be this has
> > messed things up. I suggest asking savannah-hackers@gnu.org, with a cc
> > to emacs-devel.
>
> Greetings. If what Glenn says is true, could you please reinstate the
> configuration that we had set up some time ago so that a copy of the
> diffs for MH-E (I think it was just emacs/lisp/mh-e) go to
> mh-e-devel@lists.sourceforge.net? Thank you!
We just noticed that a recent configuration change at gnu.org impacted
Savannah (more precisely: the sender aliases) which caused some mails
to be rejected, including commit notifications. People in charge are
contacted, and I setup a workaround until this is fixed.
However this isn't since "a few weeks", this is since January 7th -
please point us to relevant mails in the archives (last received,
etc.) so we can investigate.
--
Sylvain
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Savannah-help-public] MH-E diffs no longer sent to mh-e-devel
2009-01-12 8:04 ` [Savannah-help-public] " Sylvain Beucler
@ 2009-01-25 18:46 ` Bill Wohler
0 siblings, 0 replies; 3+ messages in thread
From: Bill Wohler @ 2009-01-25 18:46 UTC (permalink / raw)
To: savannah-hackers, emacs-devel, mh-e-devel
Sylvain Beucler <beuc@gnu.org> wrote:
> On Sun, Jan 11, 2009 at 08:56:24PM -0800, Bill Wohler wrote:
> > Glenn Morris <rgm@gnu.org> wrote:
> >
> > > Bill Wohler wrote (on Sat, 10 Jan 2009 at 19:59 -0800):
> > >
> > > > You know, I haven't seen the commit messages for your recent changes. Do
> > > > you know if a CVS loginfo or alias change has occurred recently? Who
> > > > should I notify about this? I had arranged to have a copy of commit
> > > > messages for emacs/lisp/mh-e go to mh-e-devel@lists.sourcforge.net.
> > >
> > > It used to be that CVS log messages went to emacs-commit, and the
> > > diffs went to emacs-diffs. Since a few weeks ago, everything goes to
> > > the diffs list (with the cvs logs as a header). It may be this has
> > > messed things up. I suggest asking savannah-hackers@gnu.org, with a cc
> > > to emacs-devel.
> >
> > Greetings. If what Glenn says is true, could you please reinstate the
> > configuration that we had set up some time ago so that a copy of the
> > diffs for MH-E (I think it was just emacs/lisp/mh-e) go to
> > mh-e-devel@lists.sourceforge.net? Thank you!
>
> We just noticed that a recent configuration change at gnu.org impacted
> Savannah (more precisely: the sender aliases) which caused some mails
> to be rejected, including commit notifications. People in charge are
> contacted, and I setup a workaround until this is fixed.
>
> However this isn't since "a few weeks", this is since January 7th -
> please point us to relevant mails in the archives (last received,
> etc.) so we can investigate.
Thanks Sylvain.
Here's one that that did not make it to mh-e-devel@lists.sourceforge.net
that was posted on the 14th, which I believe was when you think that
things were working again.
http://lists.gnu.org/archive/html/emacs-diffs/2009-01/msg00379.html
I also just now made a handful of commits in emacs/lisp/mh-e which
haven't yet made it to your archive page.
--
Bill Wohler <wohler@newt.com> http://www.newt.com/wohler/ GnuPG ID:610BD9AD
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-01-25 18:46 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-01-12 4:56 MH-E diffs no longer sent to mh-e-devel Bill Wohler
2009-01-12 8:04 ` [Savannah-help-public] " Sylvain Beucler
2009-01-25 18:46 ` Bill Wohler
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.