From owner-freebsd-arch Wed Jan 30 2: 2:22 2002 Delivered-To: freebsd-arch@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id D587B37B417 for ; Wed, 30 Jan 2002 02:02:17 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id g0U9xGr21282; Wed, 30 Jan 2002 10:59:16 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Terry Lambert Cc: Jordan Hubbard , Dallas De Atley , arch@FreeBSD.ORG Subject: Re: __P macro question In-Reply-To: Your message of "Wed, 30 Jan 2002 01:52:28 PST." <3C57C25C.4C1EB64D@mindspring.com> Date: Wed, 30 Jan 2002 10:59:16 +0100 Message-ID: <21280.1012384756@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <3C57C25C.4C1EB64D@mindspring.com>, Terry Lambert writes: >Poul, let me get this straight: people who use FreeBSD code >for uses other than what you personally use it for, and >people who take subsets of that code instead of taking the >code on an all or nothing basis like you appear to want can >"Bugger off"? No, but if we phrase it like this: People who want to use source code from FreeBSD on other systems or in other contexts than FreeBSD will have to do whatever it takes to do that. It is not FreeBSD's objective to stay diff(1) or even cc(1) compatible with every oddball platform in the world. >PS: "Terry's set of problems" includes being able to diff >FreeBSD code and NetBSD and OpenBSD code, as well as being >able to diff new FreeBSD code against old FreeBSD code, and >get something other than 400MB of cosmetic changes to header >files and function prototypes. More able hackers use scripts to deal with that problem. If you cared to think rather than preach you would quickly realize that it is simple to add __P() to prototyped include files with a script before you run diff(1). Another useful method is keeping a "baseline patch" around which contains already looked over diffs and apply that in reverse before diff'ing. Finally you would have more time to read your 400MB of diffs if you didn't wast so much time filling hot air into emails. Over and out... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message