Date: Mon, 8 Dec 1997 10:32:40 -0500 (EST) From: John Fieber <jfieber@indiana.edu> To: Thomas Gellekum <tg@ihf.rwth-aachen.de> Cc: "David E. Cross" <dec@phoenix.its.rpi.edu>, "Jordan K. Hubbard" <jkh@FreeBSD.ORG>, Andrew Stesin <stesin@gu.net>, freebsd-hackers@freefall.FreeBSD.org Subject: Re: F00F patch problems for 2.2.5-RELEASE (incomplete patch.) Message-ID: <Pine.BSF.3.96.971208101939.16632M-100000@fallout.campusview.indiana.edu> In-Reply-To: <871zzn50dl.fsf@ghpc6.ihf.rwth-aachen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8 Dec 1997, Thomas Gellekum wrote: > "David E. Cross" <dec@phoenix.its.rpi.edu> writes: > > > Yes, I would like to know how to see what the changelogs are for each > > version of a file... I know it is possible, I have seen excerpts posted > > from them here occasionally. > > http://www.freebsd.org/cgi/cvsweg.cgi > > If you have the CVS repository on your disk simply use `cvs log'. This is great for individual files, but things like the "FOOF fix" are often not represented in a single file, or even in a single commit. Identifying the relevant changes for things like this can only be done by (a) the person who committs the changes or (b) very close observers of the commit logs. Jill or Joe Casual User running a RELEASE, but wanting to keep up on security related fixes must rely on (a) or (b) providing complete and accurate information; cvsweb doesn't quite cut it and blindly upgrading to a stable kernel can have unpleasant surprises. -john
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.971208101939.16632M-100000>