Date: Sun, 28 May 1995 22:29:49 -0700 From: asami@CS.Berkeley.EDU (Satoshi Asami | =?ISO-2022-JP?B?GyRCQHUbKEI=?= =?ISO-2022-JP?B?GyRCOCsbKEIgGyRCOC0bKEI=?=) To: rgrimes@gndrsh.aac.dev.com Cc: jhs@vector.eikon.e-technik.tu-muenchen.de, ports@FreeBSD.org, gj@FreeBSD.org Subject: Re: Hylafax - a patch to fix the broken port, tested against ctm444. Message-ID: <199505290529.WAA09356@silvia.HIP.Berkeley.EDU> In-Reply-To: <199505281218.FAA05695@gndrsh.aac.dev.com> (rgrimes@gndrsh.aac.dev.com)
next in thread | previous in thread | raw e-mail | index | archive | help
* DO NOT ATTEMPT TO COMMIT THIS PATCH, it will not do what you think it will * do. The $Header$ and $Id$ strings will change to 1.2, not what you want * them to!! I know, don't worry.... ;) * I will look closely at the patch and see if I can do the patch in such * a way that it applies cleanly without looking at the RCS strings (either * narrow the context diff with a -c 2 or -c 1, or possible use a unidiff * format). I don't think changing it to unified diff will help, will it? Well anyway, most of the failing hunks are $ strings only, we can just take those out, there aren't any that are "accidentally" included because they are part of the context. It seems like the only real problem is where it is attempting to fix the version number printed by --version, I guess we'll have to leave that out too, it will print out an incorrect version but that's about it, right? I committed a version of patch-aa without all those $ strings, it patched fine and is compiling now, well see how it goes. Satoshi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199505290529.WAA09356>