Date: Wed, 21 Jan 1998 10:25:57 +0300 (MSK) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= <ache@nagual.pp.ru> To: Satoshi Asami <asami@cs.berkeley.edu> Cc: peter@netplex.com.au, perhaps@yes.no, gpalmer@FreeBSD.ORG, ports@FreeBSD.ORG, committers@FreeBSD.ORG Subject: Re: amanda port, empty PATCH_STRIP= lines causes trouble Message-ID: <Pine.BSF.3.96.980121101646.2729A-100000@lsd.relcom.eu.net> In-Reply-To: <199801210101.RAA19809@baloon.mimi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 20 Jan 1998, Satoshi Asami wrote: > I think the best thing to do is to install two version of patches > until 2.2.6 so committers running -stable don't have to dig out the > patch binary from the CD to deal with PR submissions. How about > /usr/bin/opatch for the old behavior and /usr/bin/patch for the one > with the "fix"? (This is not for bsd.port.mk use, so long names like > "broken_patch" is not practical.) If you mean "hacked" FreeBSD variant as /usr/bin/opatch and unmodified GNU variant as /usr/bin/patch, I agree. > * It seems I have bad Karma to explain in details what happens with patch to > * each and every core team member separately, because others not read > * this discussion until something not works as expected for them. > > Maybe it's worth pointing out that all the recent flame wars have been > caused by someone committing something controversial without > discussing it first. When things break, people tend to get angry. A Especially bad thing in my case that I call for discussion before commiting new patch 2.5. Nobody seems listen except Joerg says "yes". I don't know how to prevent similar situations in future :-( -- Andrey A. Chernov <ache@nietzsche.net> http://www.nagual.pp.ru/~ache/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980121101646.2729A-100000>