Date: Wed, 30 Jul 2014 07:46:20 +0000 From: Alexey Dokuchaev <danfe@FreeBSD.org> To: Mathieu Arnold <mat@FreeBSD.org> Cc: svn-ports-head@freebsd.org, Max Brazhnikov <makc@freebsd.org>, svn-ports-all@freebsd.org, marino@freebsd.org, William Grzybowski <wg@freebsd.org>, ports-committers@freebsd.org, Adam Weinberger <adamw@adamw.org> Subject: Re: svn commit: r363361 - in head/editors/fte: . files Message-ID: <20140730074620.GA14983@FreeBSD.org> In-Reply-To: <2D24420529C9ECAEABB9A791@atuin.in.mat.cc> References: <201407291646.s6TGkjHH090335@svn.freebsd.org> <41D25BC1-AC62-4280-A342-8A2BDD84B1E0@adamw.org> <20140730070412.GA97692@FreeBSD.org> <3898057.T8DsoXnEEp@mercury.ph.man.ac.uk> <53D89EBF.4080805@marino.st> <2D24420529C9ECAEABB9A791@atuin.in.mat.cc>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jul 30, 2014 at 09:37:24AM +0200, Mathieu Arnold wrote: > makepatch name convention is the convention, I find it pretty simple, and > easy to remember, it does "s|/|__|" and that's all. Whatever the And I find it totally confusing and unnatural that __ is a placeholder for path separator. I have to constantly repeat this to myself, and doing so definitely does not add to productivity. > convention, there's always someone who will not like it, but it doesn't > really matter, it's a convention so that everyone knows how to name patch > files the same way. It's not just about whether I like it or not this time. I do not like a lot of things people are doing about ports, but as long as it does not sabotage my workflow I'm fine with it. But this __ is just unbearable and makes me want to shit my eyes out. Mind you, the point is not about naming patches the same way, it's about making patch names descriptive and readable; yet __ does not take anything from the former, but greatly pessimises the latter. ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140730074620.GA14983>