Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 19 Apr 2002 07:50:48 -0500
From:      "Jacques A. Vidrine" <nectar@FreeBSD.org>
To:        Doug Barton <DougB@FreeBSD.org>
Cc:        "David E. O'Brien" <obrien@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject:   Re: cvs commit: ports/Tools/scripts patchtool.py
Message-ID:  <20020419125048.GB352@madman.nectar.cc>
In-Reply-To: <20020418175817.K8772-100000@zoot.corp.yahoo.com>
References:  <20020418192829.GA25519@madman.nectar.cc> <20020418175817.K8772-100000@zoot.corp.yahoo.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Apr 18, 2002 at 06:00:56PM -0700, Doug Barton wrote:
> On Thu, 18 Apr 2002, Jacques A. Vidrine wrote:
> 
> > 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.
> 
> 	But, but... it was YOUR point just a second ago. :)

:-)

> > OTOH, that leaves over 88% of the port patch files still using the old
> > convention or not including directory names.
> 
> 	I snipped the rest of your stats, because I think this is the
> telling item. It's not to late to fix something that looks like it might
> be broken.
> 
> > We had this same thread some time ago, and we picked a convention and
> > stuck with it
> 
> 	Pardon me for missing that discussion, but sometimes things need
> to change because operational issues (which always reach a wider audience)
> highlight problems that weren't apparent from theoretical discussions.
> It's part of life in our world.

I don't disagree.  However, (IMHO) there are no problems here, and
there is nothing broken.  Just a convention that has seen considerable
use; is simple to use; and works -- it provides an unambiguous
canonical representation of a path.  At least e.g. URL encoding wasn't
used :-)

Cheers,
-- 
Jacques A. Vidrine <n@nectar.cc>                 http://www.nectar.cc/
NTT/Verio SME          .     FreeBSD UNIX     .       Heimdal Kerberos
jvidrine@verio.net     .  nectar@FreeBSD.org  .          nectar@kth.se

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020419125048.GB352>