Date: Sun, 8 Jan 1995 19:14:10 -0800 (PST) From: "Justin T. Gibbs" <gibbs@estienne.CS.Berkeley.EDU> To: bde@zeta.org.au (Bruce Evans) Cc: dufault@hda.com, freebsd-hackers@freefall.cdrom.com Subject: Re: Commit testing Message-ID: <199501090314.TAA23236@estienne.cs.berkeley.edu> In-Reply-To: <199501090147.MAA03141@godzilla.zeta.org.au> from "Bruce Evans" at Jan 9, 95 12:47:36 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > >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 ==============================================
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199501090314.TAA23236>