Date: Mon, 12 Jan 2004 09:57:41 -0800 From: Brooks Davis <brooks@one-eyed-alien.net> To: Jamie Bowden <ragnar@sysabend.org> Cc: freebsd-current@freebsd.org Subject: Re: Look ma, the kernel don't compile no more... Message-ID: <20040112175741.GB1762@Odin.AC.HMC.Edu> In-Reply-To: <20040112072306.J78161-100000@moo.sysabend.org> References: <87d69r4tsd.fsf@strauser.com> <20040112072306.J78161-100000@moo.sysabend.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--8GpibOaaTibBMecb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 12, 2004 at 07:27:44AM -0800, Jamie Bowden wrote: > On Sat, 10 Jan 2004, Kirk Strauser wrote: >=20 > > At 2004-01-09T20:19:41Z, Jamie Bowden <ragnar@sysabend.org> writes: >=20 > > > I got a clean build after re-cvsuping (looks like I picked up 3 more > > > file changes or so, at least one to the tcp bits). This is the first > > > time my multiple cvsup system has failed me, guess I'll increase the > > > sleep time between. >=20 > > Out of curiosity, why would multiple syncs be better than just one? > > Wouldn't the final sync be the same whether you'd done several before it > > or not? >=20 > Not based on experience. I always do multiple cvsups with a timed sleep > between until I get two in a row that don't checkout new, modify, or > remove existing files. Usually three is sufficicient; the first updates > my local source and the second and third confirm that I didn't checkout > during the middle of a commit. Every now and then, I'll have to do a > fourth as the second will modify a few more files. This only deals with one of the two possiable problems. This problem is that you update while the cvsup server you are talking to is updating. This does nothing about the problem where the server you are updating =66rom updates while cvsup-master is updating from repoman[0]. There's nothing to be done about that case since the server won't update more then once an hour. -- Brooks [0] There's also the problme where cvsup-master updates in the middle of a commit, but from the user's perspective, there's no way to tell that =66rom the previous case. --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --8GpibOaaTibBMecb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFAAuAUXY6L6fI4GtQRAl2PAKC2FfOS8Cjk6wcqDFo41fGblQzGnACbBEPG Rmg2wHuY3hdKOWA7yqoqeAo= =qg11 -----END PGP SIGNATURE----- --8GpibOaaTibBMecb--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040112175741.GB1762>