From owner-freebsd-current Tue Feb 10 04:52:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA21165 for current-outgoing; Tue, 10 Feb 1998 04:52:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA21160 for ; Tue, 10 Feb 1998 04:52:27 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id EAA12823; Tue, 10 Feb 1998 04:51:59 -0800 (PST) To: Eivind Eklund cc: Terry Lambert , freebsd-current@FreeBSD.ORG Subject: Re: merging win95 and nt filesystem changes into msdosfs In-reply-to: Your message of "Tue, 10 Feb 1998 13:43:34 +0100." <19980210134334.60912@follo.net> Date: Tue, 10 Feb 1998 04:51:59 -0800 Message-ID: <12818.887115119@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm willing to try. I've been toying with just running some of Terrys > patches here and see if they're stable, attempting to test the areas they > touch, and then just commit them and take the blame (if any). I'm just not > quite certain how hard that blame is going to be, and I would dislike > loosing my commit privileges :-( In -current, you and your commit privileges are reasonably safe as long as you're at least willing to deal with any potential "this sucks because ..." arguments that may come up and, should those arguments prove convincing enough, be willing to back the changes out again. It's only the folks that get sticky over such issues that ever get the Big Stick waved at them. :-) Needless to say, you're also expected to make every reasonable effort to stress test the code on a local machine before committing it. "Well, it compiled!" is not anyone's idea of a proper acceptance test. ;) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message