Date: Thu, 02 Nov 2006 23:41:13 -0800 From: Maxim Sobolev <sobomax@FreeBSD.org> To: Sam Lawrance <lawrance@FreeBSD.org> Cc: cvs-ports@FreeBSD.org, cvs-all@FreeBSD.org, ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/devel/mpatrol Makefile ports/devel/mpatrol/files patch-..::..::src::mptrace.c Message-ID: <454AF299.30307@FreeBSD.org> In-Reply-To: <FDCC5D5B-949A-4A3B-8EAE-33DEDF272967@FreeBSD.org> References: <200611030351.kA33peWQ061783@repoman.freebsd.org> <FDCC5D5B-949A-4A3B-8EAE-33DEDF272967@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Sam Lawrance wrote: > > On 03/11/2006, at 2:51 PM, Maxim Sobolev wrote: > >> sobomax 2006-11-03 03:51:40 UTC >> >> FreeBSD ports repository >> >> Modified files: >> devel/mpatrol Makefile >> Added files: >> devel/mpatrol/files patch-..::..::src::mptrace.c >> Log: >> Unbreak on amd64. >> >> Obtained from: debian (mptrace.c patch) >> Sponsored by: Sippy Software, Inc. >> >> Revision Changes Path >> 1.3 +8 -2 ports/devel/mpatrol/Makefile >> 1.1 +44 -0 >> ports/devel/mpatrol/files/patch-..::..::src::mptrace.c (new) >> > > If you want to patch at a different level to WRKSRC, you can set > PATCH_WRKSRC. Saves having to use "..". Well, not in all cases you can do this. There could cases when patches in one port are spanning several levels. And it's not really the point. For me, those patches are managed by the automated tool, so that I don't really care about their names, and nobody should as long as the port works. I am not going to spend my time satisfying yours or anybody else's aesthetics sentiments regarding patch names, sorry. -Maxim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?454AF299.30307>