From owner-freebsd-hackers Sun Jan 8 18:42:26 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id SAA18345 for hackers-outgoing; Sun, 8 Jan 1995 18:42:26 -0800 Received: from estienne.cs.berkeley.edu (estienne.CS.Berkeley.EDU [128.32.42.147]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id SAA18339 for ; Sun, 8 Jan 1995 18:42:25 -0800 Received: (from gibbs@localhost) by estienne.cs.berkeley.edu (8.6.9/8.6.9) id TAA23236; Sun, 8 Jan 1995 19:14:11 -0800 From: "Justin T. Gibbs" Message-Id: <199501090314.TAA23236@estienne.cs.berkeley.edu> Subject: Re: Commit testing To: bde@zeta.org.au (Bruce Evans) Date: Sun, 8 Jan 1995 19:14:10 -0800 (PST) Cc: dufault@hda.com, freebsd-hackers@freefall.cdrom.com In-Reply-To: <199501090147.MAA03141@godzilla.zeta.org.au> from "Bruce Evans" at Jan 9, 95 12:47:36 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: 859 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > >Well, I usually thoroughly test my code, and when I'm ready to commit > >it, SUP current and rebuild, do about an hour or so of testing again, > >and commit. Then I re-sup, merge conflicts, and retest to see if I've > > I usually test my code for a few days or longer, merging it with > -current every day. When I commit it, I don't expect to see any > conflicts. After I commit it, I don't worry about it until a ctm > update arrives 12-24 hours later. > > Bruce > By conflicts, I mean conflicts with my own changes, since I haven't come up with a way to have CVS realize that it was me who committed the code albeit on a remote system. -- Justin T. Gibbs ============================================== TCS Instructional Group - Programmer/Analyst 1 Cory | Po | Danube | Volga | Parker | Torus ==============================================