From owner-freebsd-current Fri Aug 9 18:12:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA22642 for current-outgoing; Fri, 9 Aug 1996 18:12:21 -0700 (PDT) Received: from utgard.bga.com (utgard.bga.com [205.238.129.45]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA22637 for ; Fri, 9 Aug 1996 18:12:16 -0700 (PDT) Received: (from faulkner@localhost) by utgard.bga.com (8.7.5/8.7.3) id UAA14116; Fri, 9 Aug 1996 20:12:05 -0459 (CDT) Message-Id: <199608100111.UAA14116@utgard.bga.com> Subject: Re: Praise for CVSup To: jdp@polstra.com (John Polstra) Date: Fri, 9 Aug 1996 20:12:05 -0459 (CDT) From: "Boyd R. Faulkner" Cc: current@FreeBSD.org In-Reply-To: <199608100056.RAA24189@austin.polstra.com> from "John Polstra" at Aug 9, 96 05:56:38 pm X-Mailer: ELM [version 2.4 PL25 ME8b] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk According to John Polstra: > > > > Blessed be CVSup. Verily, I have used it and my povray problem > > hath fled in haste. > > Praise is always welcome, of course, but ... I don't understand. > You're not implying that CVSup fixed povray, are you? I was just > _sure_ I had taken out the experimental "auto-fix-bugs" feature > before I made the public release. :-) Check again. > > I wouldn't even ask this, but you said in a different posting that > CVSup had "fixed something in my tree that sup wouldn't fix." It's > sort of hard for me to imagine what that might be. If you ignore > the details, they both do the same thing. Namely, they find files > that are different on the client and server, and make them the > same. > > Can you give us some details about what you're referring to? > Actually, I am. CVSup does more file checking than sup does. You can end up with files with the right date and size but not the right contents and, while I may be wrong, sup will not detect this. Since CVSup uses MD5 (yes?) to ID the files, you are gurarnteed the correct contents. I was blowing my tree away and resupping pieces but I hadn't got very far. Whatever was bad is gone now. I can run povray without getting Floating point errors. I knew it was my tree because I had installed 2.1.5 on another drive in this box and povray had worked. Maybe I am wrong about how little checking sup does but I don't think so. Either way, it didn't work. Then it did. CVSup was the step inbetween. Thanks. Boyd > Thanks, > John > -- _____________________________________________________________________________ Boyd Faulkner "The fates lead him who will; faulkner@asgard.bga.com Him who won't, they drag." http://asgard.bga.com/~faulkner Old Roman Saying -- Source: Joseph Campbell _____________________________________________________________________________