Re: newer versions of gnu diff and patch
From: Garance A Drosihn (drosih_at_rpi.edu)
Date: 07/31/04
- Previous message: Tim Robbins: "Re: newer versions of gnu diff and patch"
- In reply to: Tim Robbins: "Re: newer versions of gnu diff and patch"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 31 Jul 2004 14:14:57 -0400 To: Tim Robbins <tjr@freebsd.org>
At 1:52 PM +1000 7/31/04, Tim Robbins wrote:
>On Fri, Jul 30, 2004, Garance A Drosihn wrote:
> > At 5:40 PM +0200 7/30/04, Radim Kolar wrote:
>> >in freebsd 5.2 i have in base system diff 2.7 and patch 2.1.
>> >Are there any plans to import newer versions into base system
>> >for 5.3 release?
>>
>> There is an explicit decision to leave diff and patch as they are.
>> The newer gnu patch is also incompatible to the older patch in
>> some ways, so it is not a trivial "just drop it in" upgrade. A
>> new version of patch *will* break some things, and we certainly
>> do not need that right now.
>>
>> What we would like to do is to move to a bsd-licensed version of
>> patch, which I am supposed to be working on in my copious spare
>> time...
>
>FWIW, I have been running with OpenBSD's version of patch on most of
>my machines for a year or more now, and haven't had any problems.
Thanks for the info. It is my intent to revive the patch-related
project that I had promised to do. I might be able to start on
that this weekend, assuming I can first track down a completely
unrelated problem that I am having on sparc64.
-- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu _______________________________________________ freebsd-arch@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-arch To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
- Previous message: Tim Robbins: "Re: newer versions of gnu diff and patch"
- In reply to: Tim Robbins: "Re: newer versions of gnu diff and patch"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
- Re: [PATCH] timekeeping fix mismerge
... clocksource resume logic patch. ... GNU patch semantics, because GNU
patch defaults to --fuzz=2, and ... scripts will apply the patch to the wrong place, and then
the diff gets ... I don't think re-generating the diff is wrong, and in fact I think
you ... (Linux-Kernel) - Success! was Re: tvtime audio vs pcHDTV-3000 card and pvHDTV-1.6 software
... On Wednesday 16 March 2005 20:15, Gene Heskett wrote: ... > that a diff
actually outputs only the src code differences, ... nor in that simple little 10 line patch
that ... >Unforch, the 2.6.11 plain tree has not, in this case been built yet ...
(Linux-Kernel) - Re: how to compile and install a new driver
... Warren Block wrote: ... but you'd better include enough info so that they could
make FreeBSD-stype diffs: diff has the unfortunate default of making an output that is compatible
with ed. ... This supplies extremely little information to use, in case the file you're trying
to patch with that diff has changed, and is also damned hard for mere humans to understand. ...
then you can compile. ... (freebsd-questions) - [PATCH][CFT] mm swapping improvements
... Nikita's patches and one of my own, and backs out the RSS limit patch ... diff
-puN include/linux/mmzone.h~rollup include/linux/mmzone.h ... -int FASTCALL); ...
(Linux-Kernel) - Re: Reading and applying patches
... It's worth mentioning that patch is pretty forgiving. ... text up to the actual
patch data (the output of a diff command, ... often the "old" tree will be inside
... Commands like "cvs diff" will generate diff output, ... (Fedora)