Date: Tue, 28 Apr 1998 06:26:11 -0500 From: Richard Wackerbarth <rkw@dataplex.net> To: Chuck Robey <chuckr@glue.umd.edu> Cc: Ollivier Robert <roberto@keltia.freenix.fr>, hackers@FreeBSD.ORG, Warner Losh <imp@village.org> Subject: Re: ctm question Message-ID: <l03130300b16b68bf1d56@[208.2.87.7]> In-Reply-To: <Pine.BSF.3.96.980428023815.303X-100000@localhost> References: <19980428075429.A8984@keltia.freenix.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
At 1:39 AM -0500 4/28/98, Chuck Robey wrote: >On Tue, 28 Apr 1998, Ollivier Robert wrote: > >> According to Warner Losh: >> > touch those things that whose md5 doesn't match, but do touch those >> > that do" so that I have at least a hope of restoring my local CVS tree >> > w/o having to fetch the latest all snapshot. >> >> Use CVSup from ctm.freebsd.org, it is updated by CTM so you're sure it is >> synchronised. Its main problem is that it doesn't maintain the .ctm_status >> file. > >Why not? It seems that would make re-syncing the ctm damn near >impossible ... Not really. You know that it is synced to some recent ctm update. (Actually, it is synced the the ctm-cvs feed. Not every cvs update affects each branch feed.) Just look at the past update or two and see if it has already been applied. When you find the last one which was applied, you are in business. Perhaps an easier way would be to CVSup to update your tree. Then insert a .ctm_status file that is known to be a bit too early. Try to apply the update stream. As each update fails, bump the number in .ctm_status and try the next one. I venture to quess that you will need only one or two "false starts". You will probably have to wait for the next update to arrive before you find one to apply. Richard Wackerbarth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?l03130300b16b68bf1d56>