Date: Fri, 26 Apr 2002 14:22:52 -0600 (MDT) From: "M. Warner Losh" <imp@village.org> To: green@FreeBSD.ORG Cc: drosih@rpi.edu, areilly@bigpond.net.au, arch@FreeBSD.ORG, freebsd-standards@FreeBSD.ORG Subject: Re: diff & patch problem with 'No newline' Message-ID: <20020426.142252.15670459.imp@village.org> In-Reply-To: <200204262019.g3QKJSs87524@green.bikeshed.org> References: <20020426.095955.80136029.imp@village.org> <200204262019.g3QKJSs87524@green.bikeshed.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <200204262019.g3QKJSs87524@green.bikeshed.org>
"Brian F. Feldman" <green@FreeBSD.ORG> writes:
: So, as a solution for unbreaking old machines which won't understand what to
: do with those patch files (as largely demonstrated by the ports, of course),
: should there be a port for a "new" version of patch which the ports system
: can depend upon and use instead of the base system's patch? I can see this
: mattering because people are very comfortable running releases from several
: years ago.
That's a problem for ports people to deal with :-) They routinely
have stuff like this.
I think we should MFC the patch changes for 4.6, but wait for the diff
changes for 4.7 so that we have a patch that can grok the stuff for at
least three months before we have a diff in -stable that will generate
them.
Warner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020426.142252.15670459.imp>