Date: Sat, 19 Oct 2002 21:00:58 +0300 From: Maxim Sobolev <sobomax@FreeBSD.ORG> To: Martin Blapp <mb@imp.ch> Cc: "David O'Brien" <obrien@FreeBSD.ORG>, Martin Blapp <mbr@FreeBSD.ORG>, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: ports/editors/openoffice-devel/files patch-berkeleydb::db-3.2.9.patch patch-bridges::prj::build.lst patch-bridges::source::cpp_uno::gcc2_freebsd_intel patch-bridges::source::cpp_uno::g Message-ID: <20021019180058.GA99749@vega.vega.com> In-Reply-To: <20021019191529.W90671-100000@levais.imp.ch> References: <20021019165729.GC17186@dragon.nuxi.com> <20021019191529.W90671-100000@levais.imp.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Oct 19, 2002 at 07:17:39PM +0200, Martin Blapp wrote: > > hi, > > > Couldn't you PLEASE use a single character for the path seperator?? > > If you use the port that helps create such patches as these; you can > > specify the path seperator string. > > Sound like a good idea. But I like to keep the patch names consistent. > > So does it bother you if I change all patches to this way ? And I > think this is something a repo-meister needs to do, isn't it ? I > do not want to loose all information. > > A better idea would also be to find a char which separates, and > which gets treated as a normal char form bash. Not a big deal, because shell's autocompletion routine in most cases properly escapes it with `\'. -Maxim 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?20021019180058.GA99749>