[Moved to -hubs, BCC'd to -current]

John Polstra <[EMAIL PROTECTED]> writes:
> In article <[EMAIL PROTECTED]>,
> Mike Barcroft  <[EMAIL PROTECTED]> wrote:
> > It appears this was the problem.  Switching to cvsup2.FreeBSD.org
> > seems to have have solved it.  I assume this is a result of the S1G
> > bug in cvsup.  FYI: I was using cvsup.ca.FreeBSD.org.
> Not intending to single out you folks in particular, but ...
> Just a reminder, people: Please, if you think something is wrong
> with a CVSup mirror, write to the maintainer of that mirror and tell
> him.  All of the maintainers' e-mail addresses are listed in the
> Handbook:
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html#CVSUP-MIRRORS
> It doesn't do any good to tell the -current list; you have to tell
> the maintainer or the problem won't get fixed.

I was actually intending to contact the maintainer, but it looks like
the problem has already been fixed.

Would it be possible for us to be more proactive and check to make
sure all the offical CVSup mirrors are running the corrected version?

Best regards,
Mike Barcroft

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to