From owner-freebsd-hackers Sat Jan 7 09:25:15 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id JAA22336 for hackers-outgoing; Sat, 7 Jan 1995 09:25:15 -0800 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id JAA22327 for ; Sat, 7 Jan 1995 09:25:12 -0800 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id MAA08014; Sat, 7 Jan 1995 12:26:07 -0500 From: Peter Dufault Message-Id: <199501071726.MAA08014@hda.com> Subject: Commit testing To: freebsd-hackers@freefall.cdrom.com Date: Sat, 7 Jan 1995 12:26:07 -0500 (EST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 659 Sender: hackers-owner@FreeBSD.org Precedence: bulk How do committers test things? I want to commit changes to sys/scsi/* and sys/i386/isa/aha1542.c. (the diffs, if you want to see them, are on freefall in pub:incoming/sutar7.gz) How do you handle the time between when you've thoroughly tested something and you then check it into -current? By hoping and watching commit logs? And does anyone review changes before they are commited, and what is that process? Peter -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 -- Formerly hd@world.std.com. E-mail problems? Tell hdslip@iii.net