> On Dec 16, 2016, at 15:54, Bob Proulx wrote:
>>
>> On the other hand, acco...@savannah.gnu.org seems to redirect to
>> the registered email; not sure what version we really want.
>
> Thank you for reporting this. It pointed me to the real problem.
> Which I think I have
On Fri, Dec 16, 2016 at 08:11:52AM -0500, Ineiev wrote:
>
> I see; now they look like from acco...@savannah.gnu.org, they used
> to be from the registered email (ine...@gnu.org in my case).
On the other hand, acco...@savannah.gnu.org seems to redirect to
the registered email; not sure what
On Fri, Dec 16, 2016 at 03:18:16AM -0700, Bob Proulx wrote:
> Ineiev wrote:
> > It looks like commit notifications don't come to www-comm...@gnu.org.
>
> I saw many messages from new senders to www-commits this night that
> were in the hold queue. I approved them and sent them on.
I see; now
Ineiev wrote:
> It looks like commit notifications don't come to www-comm...@gnu.org.
I saw many messages from new senders to www-commits this night that
were in the hold queue. I approved them and sent them on. They were
held only because it was a new sender. The initial contact from a new
Hello,
On Thu, Dec 15, 2016 at 10:40:37PM -0500, Assaf Gordon wrote:
>
> If you encounter any cvs related issues with savannah,
> or with web pages not being updated - please email us at
> savannah-hackers-public@gnu.org .
It looks like commit notifications don't come to www-comm...@gnu.org.
On behalf of the Savannah Hackers team...
Savannah's cvs service has been moved onto the new server.
All should be working normally but at the new IP address of the new server.
This includes projects using cvs for source code,
and all web cvs repositories for www.gnu.org/www.nongnu.org .
If you