Posted by: Administrator
on December 12, 2003 08:08 PM
> (gzcat<nobr> <wbr></nobr>../foo.patch.gz | patch -p1)? Why not "patch<nobr> <wbr></nobr>../foo.patch.gz"?
You *could* use "patch -i<nobr> <wbr></nobr>../foo.patch", provided that foo.patch has already been decompressed.
And the answer to your question lies deep in the Unix philosophy: have small tools that do one thing well, and combine them to achieve composite results. There's really on point in patch's knowing how to deal with gz files. I personally do not use gzipped patches, but rather bzip2ed ones. Someone else might prefer patching directly from the Internet (wget -O- -q http://kernel.org/pub/linux/kernel/v2.4/patch-2.4<nobr>.<wbr></nobr> 23.bz2 | bzcat | patch). You see where I'm going<nobr> <wbr></nobr>;)
Reading ESR's nice book The Art of Unix Programming (readable online at ) might give do you good. Don't get intimidated by the title, it really has little to do with programming details but gives you some ideas of why Unix is what it is today and what facilities have traditionally been available to develop software on it.
Learn about Linux
Download Linux
Get Linux help
Re:cdrecord sucks.
Posted by: Administrator on December 12, 2003 08:08 PMYou *could* use "patch -i<nobr> <wbr></nobr>../foo.patch", provided that foo.patch has already been decompressed.
And the answer to your question lies deep in the Unix philosophy: have small tools that do one thing well, and combine them to achieve composite results. There's really on point in patch's knowing how to deal with gz files. I personally do not use gzipped patches, but rather bzip2ed ones. Someone else might prefer patching directly from the Internet (wget -O- -q http://kernel.org/pub/linux/kernel/v2.4/patch-2.4<nobr>.<wbr></nobr> 23.bz2 | bzcat | patch). You see where I'm going<nobr> <wbr></nobr>;)
Reading ESR's nice book The Art of Unix Programming (readable online at ) might give do you good. Don't get intimidated by the title, it really has little to do with programming details but gives you some ideas of why Unix is what it is today and what facilities have traditionally been available to develop software on it.
#