Date: Sun, 13 Aug 2000 01:16:03 -0700 From: "David O'Brien" <obrien@FreeBSD.ORG> To: Warner Losh <imp@village.org> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Build breakage (was: fail to compile kernel...) Message-ID: <20000813011603.B4215@dragon.nuxi.com> In-Reply-To: <200008130714.BAA07153@harmony.village.org>; from imp@village.org on Sun, Aug 13, 2000 at 01:14:09AM -0600 References: <14742.15675.412839.269577@guru.mired.org> <14742.14082.837564.871879@guru.mired.org> <Pine.BSF.4.10.10008131504560.77390-100000@RedDust.BlueSky.net.au> <200008130553.XAA06673@harmony.village.org> <14742.15675.412839.269577@guru.mired.org> <200008130714.BAA07153@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Aug 13, 2000 at 01:14:09AM -0600, Warner Losh wrote: > : Won't the 'cvs diff' command tell you about such things? If not, > : that's yet another argument for ditching cvs in favor of something > : without so many flaws (like Perforce). > > Not when the files are in multiple different directories and you have > mutliple patches cooking in your tree. I committed files in > sys/pccard, but they depended on one in sys/dev/pccard which I > honestly thought I'd checked in with an earlier newcard fix. I'd been > running the patches long enough that I basically forgot. Which is why I keep a virgin src checkout and I CVSup (with "-i") right after large commit and try building the code again in the virgin tree. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000813011603.B4215>