From owner-cvs-all Thu Apr 18 12:28:35 2002 Delivered-To: cvs-all@freebsd.org Received: from gw.nectar.cc (gw.nectar.cc [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id 9956F37B400; Thu, 18 Apr 2002 12:28:30 -0700 (PDT) Received: from madman.nectar.cc (madman.nectar.cc [10.0.1.111]) by gw.nectar.cc (Postfix) with ESMTP id B31723A; Thu, 18 Apr 2002 14:28:29 -0500 (CDT) Received: from madman.nectar.cc (localhost [IPv6:::1]) by madman.nectar.cc (8.12.2/8.11.6) with ESMTP id g3IJST0G026546; Thu, 18 Apr 2002 14:28:29 -0500 (CDT) (envelope-from nectar@madman.nectar.cc) Received: (from nectar@localhost) by madman.nectar.cc (8.12.2/8.12.2/Submit) id g3IJSTYV026545; Thu, 18 Apr 2002 14:28:29 -0500 (CDT) Date: Thu, 18 Apr 2002 14:28:29 -0500 From: "Jacques A. Vidrine" To: Doug Barton Cc: "David E. O'Brien" , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: ports/Tools/scripts patchtool.py Message-ID: <20020418192829.GA25519@madman.nectar.cc> Mail-Followup-To: "Jacques A. Vidrine" , Doug Barton , "David E. O'Brien" , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org References: <20020418175216.GA24952@madman.nectar.cc> <20020418114950.R9140-100000@master.gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020418114950.R9140-100000@master.gorean.org> User-Agent: Mutt/1.3.28i X-Url: http://www.nectar.cc/ Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Apr 18, 2002 at 11:50:59AM -0700, Doug Barton wrote: > On Thu, 18 Apr 2002, Jacques A. Vidrine wrote: > > > IMHO there was value in doing it in one consistent, mostly unambiguous > > fashion, even if it wasn't `perfect'. `_' isn't perfect either, IMHO, > > and I'd rather not change just because it is someone's pet peeve. > > One could argue that the :: convention came after some of us had > already started using _, but without making so much noise about it. One could, but I don't think that's the point. My ports repository includes 11,180 patch files. Of these: = 1,032 (over 9%) have `::' in the pathname. = 262 (over 2%) have '_' in the pathname. Many of those in the second bullet are `false positives', in that `_' is used sometimes in the actual distribution pathnames or a `_' was used for some inexplicable reason (e.g. audio/csound/files/patch-main_c). So there are at least four times as many patches which use `::' over `_'. OTOH, that leaves over 88% of the port patch files still using the old convention or not including directory names. We had this same thread some time ago, and we picked a convention and stuck with it [1]. Again, with no compelling reason to change, it is hard to take the suggestion seriously. Cheers, -- Jacques A. Vidrine http://www.nectar.cc/ NTT/Verio SME . FreeBSD UNIX . Heimdal Kerberos jvidrine@verio.net . nectar@FreeBSD.org . nectar@kth.se [1] During that discussion, I felt that a port maintainer should manage the patches in any reasonable fashion he likes. However, given no other strong convictions, please follow convention. I still feel the same. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message