From owner-freebsd-ports Wed Jan 21 00:39:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA04530 for freebsd-ports-outgoing; Wed, 21 Jan 1998 00:39:46 -0800 (PST) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from baloon.mimi.com (sjx-ca126-30.ix.netcom.com [207.92.177.222]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA04504; Wed, 21 Jan 1998 00:39:38 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: (from asami@localhost) by baloon.mimi.com (8.8.8/8.8.8) id AAA20720; Wed, 21 Jan 1998 00:39:23 -0800 (PST) (envelope-from asami) Date: Wed, 21 Jan 1998 00:39:23 -0800 (PST) Message-Id: <199801210839.AAA20720@baloon.mimi.com> To: ache@nagual.pp.ru CC: peter@netplex.com.au, perhaps@yes.no, gpalmer@FreeBSD.ORG, ports@FreeBSD.ORG, committers@FreeBSD.ORG In-reply-to: (message from =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= on Wed, 21 Jan 1998 10:25:57 +0300 (MSK)) Subject: Re: amanda port, empty PATCH_STRIP= lines causes trouble From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * If you mean "hacked" FreeBSD variant as /usr/bin/opatch and unmodified GNU * variant as /usr/bin/patch, I agree. Yes. * 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 :-( That's not my point of view. There was a commit to back out the cvs-compat hack, Joerg and you got into an argument, I followed it a while but it got so long and winding I sort of lost it, then there was a commit of patch 2.5. I'm sure you proposed upgrading patch to 2.5 but honestly I didn't realize you said so until I saw the import message. Although I can't speak of others, I think this is how many people saw it. Satoshi