Date: Mon, 04 Aug 2003 21:40:58 +0200 From: Rolf Grossmann <rg@progtech.net> To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= <des@des.no> Cc: freebsd-hackers@freebsd.org Subject: Re: Using CVS diff to find out what has changed, including new files Message-ID: <3F2EB6CA.5000102@PROGTECH.net> In-Reply-To: <xzpptjlp7qp.fsf@dwp.des.no> References: <200308041304.h74D4u000654@isis.muc.progtech.intern> <xzpptjlp7qp.fsf@dwp.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
Dag-Erling Smørgrav wrote: >Rolf Grossmann <grossman@progtech.net> writes: > > >>I'm using cvsup for a while now to get a copy of the FreeBSD CVS repository >>and I have a (slightly modified) version of -STABLE checked out from there. >>Now there are certain areas where I'd like to see what changed before >>doing a "cvs update". Currently I'm using "cvs diff -u -N -r BASE -r RELENG_4" >>to do that. However this has one drawback that I'm hoping you'll be >>able to help me with: If files have been removed from the distribution, >>these files continue to show up as getting readded (even though they >>won't when doing an update). To see the problem, you can go to >>/usr/src/sbin/md5 and run the above cvs diff command. >> >> > >That's normal behaviour with CVS when using branches. > FWIW it also happens with HEAD (which of course is a branch aswell, but no way around). >The only >workaround I know of is to specify the files explicitly. With zsh, >you can do 'cvs diff -Nu -rBASE -rRELENG_4 **/*~*CVS*(.)' > Which, again, won't list the files I don't have yet. Wouldn't you consider it a bug listing files that are not really part of either revision? Maybe I should file a bug report with the CVS people? Anyway, thanks a lot for your reply. Rolf
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F2EB6CA.5000102>