Re: portsnap and the imminent demise of svn->cvs ports tree export

2013-01-25 Thread Thomas Mueller
> >Date: Mon, 21 Jan 2013 12:01:05 +1100 > How do you work that out? None of the headers you've included show > any problem. John sent his mail at 010105UT on 21st, and your headers > say you received it at 095334UT on 21st - nearly 9 hours later. The > X-Apparently-To header is 010132UT on the

Re: portsnap and the imminent demise of svn->cvs ports tree export

2013-01-23 Thread Simon L. B. Nielsen
On 21 January 2013 01:01, John Marshall wrote: > We are on notice that the current ports tree will be soon no longer > available via CVSup and friends. General consumers of the FreeBSD ports > tree are being encouraged to switch to portsnap. > > http://lists.freebsd.org/pipermail/freebsd-ports-an

Re: portsnap and the imminent demise of svn->cvs ports tree export

2013-01-23 Thread Peter Jeremy
On 2013-Jan-22 22:45:24 -0500, Thomas Mueller wrote: >Your date is ahead of what the headers of your message say: > >>From owner-freebsd-po...@freebsd.org Mon Jan 21 09:53:34 2013 >Received: from pop.att.yahoo.com (pop2.sbc.mail.vip.ne1.yahoo.com >[98.138.197.207]) >by mueller6722.bellsou

Re: portsnap and the imminent demise of svn->cvs ports tree export

2013-01-22 Thread Thomas Mueller
> > (current time: Wed 23 Jan 2013 02:43:43 AM UTC) --] > [-- End of PGP output --] > [-- The following data is signed --] > We are on notice that the current ports tree will be soon no longer > available via CVSup and friends. General consumers of the FreeBSD ports > tree are being encouraged