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 ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- Re: fail to compile kernel... Warner Losh
- Re: fail to compile kernel... Idea Receiver
- fail to compile kernel... Mike Meyer
- Re: fail to compile kernel... Warner Losh
- Build breakage (was: fail to compile kernel...) Mike Meyer
- Re: Build breakage (was: fail to compile kernel...) Leif Neland
- Re: Build breakage (was: fail to compile kernel...) Warner Losh
- Re: Build breakage (was: fail to compile kernel...) John Polstra
- Re: Build breakage (was: fail to compile kernel...) Warner Losh
- Re: Build breakage (was: fail to compile kernel...) David O'Brien
- Re: Build breakage (was: fail to compile kernel...) Mike Meyer
- Re: Build breakage (was: fail to compile kernel...) Warner Losh
- Re: Build breakage (was: fail to compile kernel...) Warner Losh
- Re: Build breakage (was: fail to compile kernel... Mike Meyer
- Re: Build breakage (was: fail to compile ke... John Polstra
- Re: Build breakage (was: fail to compile kernel... Warner Losh