From owner-freebsd-arch Wed Jan 30 2:18:22 2002 Delivered-To: freebsd-arch@freebsd.org Received: from scaup.prod.itd.earthlink.net (scaup.mail.pas.earthlink.net [207.217.120.49]) by hub.freebsd.org (Postfix) with ESMTP id C9BA737B400 for ; Wed, 30 Jan 2002 02:18:19 -0800 (PST) Received: from pool0125.cvx40-bradley.dialup.earthlink.net ([216.244.42.125] helo=mindspring.com) by scaup.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16Vrof-0005sD-00; Wed, 30 Jan 2002 02:18:09 -0800 Message-ID: <3C57C858.5FCC9453@mindspring.com> Date: Wed, 30 Jan 2002 02:18:00 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Poul-Henning Kamp Cc: Jordan Hubbard , Dallas De Atley , arch@FreeBSD.ORG Subject: Re: __P macro question References: <21280.1012384756@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 Poul-Henning Kamp wrote: > 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. You mean "portable to", not "compatible with". If the intent is no longer to act as a reference implementation for various code, then perhaps we should reconsider and release all of FreeBSD under the GPL, so it will be even more useless as a use-agnostic reference implementation. > >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. More able hackers use scripts to remove "offensive" things like "__P()" or even the contents of "#ifdef ALPHA" or other noop code for the platform they are using, rather than rendering the base code non-protable to all but their pet machines. > Another useful method is keeping a "baseline patch" around which > contains already looked over diffs and apply that in reverse before > diff'ing. Won't work in the context of back-porting from an unstable -current to a -stable a necessary patch, when you don't want to have to drink the "kernel interrupt threads" and other instability causing koolaid. > 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. Thanks for your concern, but I read very quickly. My concern was more general than for just myself. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message