Bill LaGrue wrote: > Hi Phil > Forgive my ignorance...but how do you apply the patch? I'm getting > 'Hunk failed' errors, so I'm obviously not doing it right..
Check out a new clean repo (mis-applied patches change things in bad ways), and from the top-level directory: patch -p0 < /tmp/libconcord-connectivity.patch You can do a dry-run first: patch -p0 --dry-run < /tmp/libconcord-connectivity.patch to make sure it's going to apply cleanly. It should look like this: [EMAIL PROTECTED] concordance]$ cvs co concordance ... [EMAIL PROTECTED] tmp]$ cd concordance/ [EMAIL PROTECTED] concordance]$ ls CVS INSTALL.mac concordance examples specs INSTALL.linux INSTALL.windows consnoop libconcord win [EMAIL PROTECTED] concordance]$ patch -p0 --dry-run </tmp/libconcord-connectivity.patch patching file libconcord/web.cpp [EMAIL PROTECTED] concordance]$ patch -p0 </tmp/libconcord-connectivity.patch patching file libconcord/web.cpp [EMAIL PROTECTED] concordance]$ -- Phil Dibowitz [EMAIL PROTECTED] Open Source software and tech docs Insanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ "Never write it in C if you can do it in 'awk'; Never do it in 'awk' if 'sed' can handle it; Never use 'sed' when 'tr' can do the job; Never invoke 'tr' when 'cat' is sufficient; Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
