From owner-freebsd-questions@FreeBSD.ORG Mon Jun 7 21:05:04 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 451A116A4ED for ; Mon, 7 Jun 2004 21:05:04 +0000 (GMT) Received: from gamera.svk.isite.net (mail.isite.net [205.217.158.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2EE0543D1D for ; Mon, 7 Jun 2004 21:05:04 +0000 (GMT) (envelope-from jrhett@isite.net) Received: from anubis.svk.isite.net (anubis.svk.isite.net [205.217.158.5]) by gamera.svk.isite.net (8.12.10/8.12.9) with ESMTP id i57L52qa004140 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 7 Jun 2004 14:05:02 -0700 (PDT) Received: from anubis.svk.isite.net (localhost [127.0.0.1]) i57L52Z8027693; Mon, 7 Jun 2004 14:05:02 -0700 (PDT) Received: (from jrhett@localhost)i57L52DT027692; Mon, 7 Jun 2004 14:05:02 -0700 (PDT) Date: Mon, 7 Jun 2004 14:05:02 -0700 From: Joe Rhett To: Daniela Message-ID: <20040607210502.GF22403@isite.net> Mail-Followup-To: Daniela , "Goodleaf, John" , freebsd-questions@freebsd.org References: <200406072155.10022.dgw@liwest.at> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200406072155.10022.dgw@liwest.at> User-Agent: Mutt/1.4.2i Organization: Isite Services, Inc. cc: "Goodleaf, John" cc: freebsd-questions@freebsd.org Subject: Re: OT: group coding standards X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jun 2004 21:05:04 -0000 On Mon, Jun 07, 2004 at 09:55:10PM +0000, Daniela wrote: > I would have no problems with coding standards that allow you to clean up > _after_ a session, because I lose half of my good ideas while bothering with > coding standards. Good would be some convention where you can just modify > your code with sed(1) afterwards, that's not much overhead. I guess that depends on your commit policy for changes. We commit often, so here it is very important that the coding policy be something that people are very comfortable using all of the time. Way off topic, and way way opinion ;-) -- Joe Rhett Chief Geek JRhett@Isite.Net Isite Services, Inc.