Date: Wed, 21 Apr 2004 14:23:06 +0700 From: Alexey Dokuchaev <danfe@nsu.ru> To: "David O'Brien" <obrien@freebsd.org> Cc: ports-committers@freebsd.org Subject: Re: cvs commit: ports/games Makefile ports/games/duke3d Makefile distinfo pkg-descr pkg-message pkg-plist ports/games/duke3d/files README.bsd fix.sh patch-aa patch-ab patch-ac patch-ad patch-ae wrapper.sh Message-ID: <20040421072306.GA79328@regency.nsu.ru> In-Reply-To: <20040420200903.GA6174@dragon.nuxi.com> References: <200404181922.i3IJMkTf044706@repoman.freebsd.org> <20040419032304.GA61048@regency.nsu.ru> <20040419103101.GB26102@dragon.nuxi.com> <20040419110810.GA24385@regency.nsu.ru> <20040420200903.GA6174@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 20, 2004 at 01:09:03PM -0700, David O'Brien wrote: > On Mon, Apr 19, 2004 at 06:08:10PM +0700, Alexey Dokuchaev wrote: > > While particular choice for a separator is arguable, the general scheme > > for patch-files is not, right? FWIW, that was my point, not `::' vs. > > whatever. > > > > As a side note, I don't really see any problem with `::' or `-'. > > 1. Bash escapes it so it actually becomes 4 characters. > This should not be takeing lightly -- people bitched about '%' in > patch names and they were all changed because its a magic charter for > Perforce and Perforce users could be bothered to escape it. > > 2. With the file name lenths of some of our patches (greater than 80 > chars) two characters, when one will do, is annoying. > > > Contrary, `_' occurs a lot more frequently in filenames, so... > > '%' and '+' also works for me. :-) OK, fair enough. I'll consider switching to `+'. Thank you. ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040421072306.GA79328>