Date: Sat, 16 Mar 2013 15:09:20 +1100 From: John Marshall <john.marshall@riverwillow.com.au> To: freebsd-hubs@freebsd.org Subject: Re: CVSup Mirror Statistics Timestamp Problem Message-ID: <20130316040920.GA61096@rwpc15.mby.riverwillow.net.au> In-Reply-To: <20121226193919.GA90824@rwpc15.mby.riverwillow.net.au> References: <20120830232937.GE61657@rwpc15.mby.riverwillow.net.au> <20121226193919.GA90824@rwpc15.mby.riverwillow.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
--SLDf9lqlvOQaIe6s Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, 27 Dec 2012, 06:39 +1100, John Marshall wrote: > On Fri, 31 Aug 2012, 09:29 +1000, John Marshall wrote: > > Any suggestions? >=20 > A few weeks ago I found an answer. It looks like the svn-->cvs exporter > is now adding the file src/LASTCOMMIT.txt which contains the svn commit > timestamp and log message from the most recent commit. I am using the > timestamp in that svn commit message as the timestamp for determining > the age of CVSup mirrors. "It works for me". >=20 > http://www.riverwillow.net.au/~john/mirmon/cvsup.html That worked well until about 24 hours ago. I had been checking out the HEAD version of src/LASTCOMMIT.txt,v and extracting the svn commit log timestamp from that. It appears that HEAD is no longer being exported to cvs but RELENG_9 is, so I now checkout the latest from the RELENG_9 branch of src/LASTCOMMIT.txt,v and use the svn commit log timestamp to determine the age of the CVSup mirrors. --=20 John Marshall --SLDf9lqlvOQaIe6s Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlFD8HAACgkQw/tAaKKahKKUOgCdEEczM8u+xQnte05WFCKxsewo M90An2xJW8+Bnzxwc2FqpondlN6njDVZ =MhuJ -----END PGP SIGNATURE----- --SLDf9lqlvOQaIe6s--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130316040920.GA61096>