Date: Wed, 30 Jul 2014 09:29:03 +0200 From: John Marino <freebsd.contact@marino.st> To: Max Brazhnikov <makc@freebsd.org>, Alexey Dokuchaev <danfe@freebsd.org> Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org, William Grzybowski <wg@freebsd.org>, Adam Weinberger <adamw@adamw.org> Subject: Re: svn commit: r363361 - in head/editors/fte: . files Message-ID: <53D89EBF.4080805@marino.st> In-Reply-To: <3898057.T8DsoXnEEp@mercury.ph.man.ac.uk> References: <201407291646.s6TGkjHH090335@svn.freebsd.org> <41D25BC1-AC62-4280-A342-8A2BDD84B1E0@adamw.org> <20140730070412.GA97692@FreeBSD.org> <3898057.T8DsoXnEEp@mercury.ph.man.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On 7/30/2014 09:25, Max Brazhnikov wrote: > On Wed, 30 Jul 2014 07:04:13 +0000 Alexey Dokuchaev wrote: >> On Tue, Jul 29, 2014 at 01:10:45PM -0400, Adam Weinberger wrote: >>> I'm about to rename all patches that contain ::. Can we please stop >>> producing patches with :: as a path separator, and use __ instead? >> >> Can we also stop using double underscore as it makes patch names so ugly >> and unreadable that I have to spend twice as much time working on ports >> that uses this stupid convention? > > It comes from the makepatch target. Makepatch name convention is no good. I was complaining about this (to bapt) about the lack of a patch name convention and he said to propose one. I've been meaning to do just that, but it also means fixing tools like this. > >> There are plenty of nice, single characters to chose from: -, _, and + >> should suffice most needs (yes, this also covers avoiding confusion that >> original "double underscore" convention was trying to solve). > > What about U+00A0 :) er, no. :) John
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53D89EBF.4080805>