From owner-freebsd-current Fri Jun 2 23:19:08 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA05499 for current-outgoing; Fri, 2 Jun 1995 23:19:08 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA05490 for ; Fri, 2 Jun 1995 23:19:05 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id XAA09594; Fri, 2 Jun 1995 23:18:30 -0700 From: "Rodney W. Grimes" Message-Id: <199506030618.XAA09594@gndrsh.aac.dev.com> Subject: Re: sup is fetching whole src tree To: bde@zeta.org.au (Bruce Evans) Date: Fri, 2 Jun 1995 23:18:30 -0700 (PDT) Cc: bde@zeta.org.au, freebsd-current@FreeBSD.ORG In-Reply-To: <199506030607.QAA03807@godzilla.zeta.org.au> from "Bruce Evans" at Jun 3, 95 04:07:31 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2135 Sender: current-owner@FreeBSD.ORG Precedence: bulk > > >> I haven't found much use for the uncompressed commit logs either. > > >Except when you want to see what *group* of files comprized a commit, > >as a person who often has to track things down these log files are > >priceless. > > >I will agree for joy blow average commiter they are not needed, but > >if you have ever had to go pull a whole patch out of the tree as > >it was commited the only way to find it is in these log files! > > Good luck for extracting the `trailing whitespace' changes from the > info in the current log files :-). You get a complete list of the > files but not revision numbers. Well, I happen to know right where that sits, so it is a bad example, it will be the revision right after the 2.0.5A tag. I could also use the date of the commit log entry to get to those files. Remeber there is both cvs -r and cvs -D options. > Cross referencing in cvs seems weak. Is this because I don't know > any admin commands? Your right cross referencing is very poor. I find the commit in the log files and then stuff them into a file and turn it into a small shell script that does grep -A 8 filename to find the version numbers. It is a pain!! > There are many log messages that tell you about > dozens of files changed except of course for the file that you are > interested in. Sometimes it is important to commit a bunch of > interdependent changes at the same time for consistency, and then > `cvs commit' doesn't allow the log message to vary for files in the > same directory. cvs commit *does* allow the log message to vary for the files in the same directory, you just have to use it more intelegently. cvs commit -m 'message for first set of files' file1 file2 file3; cvs commit -m 'message for second set of files' file3 file4 file5; :-) And if they fixed the bugs with pathnames to files on a commit command in CVS 1.4 (have not tested this so don't know) the fileN above should be able to be paths and not just simple files. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD