Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Thu, Sep 23, 2004 at 01:09:09PM -0700, Matthew Kent wrote:
> On Thu, 2004-09-23 at 11:33, jeff vier wrote:
> > Yes, I understand what is supposed to happen, but what I'm saying is
> > that it didn't for me, and I tried it against current, stock cvs code.
> doesn't work. Then I must be seeing things!
I just tried applying the patch and it completed cleanly. How
are you extracting the patch from the original email? Copy /
Paste is probably not a good idea; you should do a save-as from
the attachment. Also make sure any FTPing you are doing is in
the appropriate mode.
The md5sum from the patch I used is:
0a7d08e1b4593ec3a6455df1d0d25d70 nagios-2.0a1-speedup_status.patch
I posted the patch file for you here: http://tinyurl.com/62yle
Perhaps it would help to do a save-as from your browser from
that URL, or better yet a wget/curl from the host on which you
are applying the patch.=20
Patch output:
Script started on Thu Sep 23 12:43:31 2004
$ cvs -d:pserver:[email protected]:/cvsroot/nagios login
Logging in to :pserver:[email protected]:2401/cvsroot/nagios
CVS password:
$ cvs -Q -z3 -d:pserver:[email protected]:/cvsroot/nagios co na=
gios
$ patch -p0 < /tmp/nagios-2.0a1-speedup_status.patch
patching file nagios/common/statusdata.c
patching file nagios/include/statusdata.h
patching file nagios/xdata/xsddefault.c
$
Script done on Thu Sep 23 12:44:14 2004
-Jason Martin
--=20
This message is PGP/MIME signed.
--U5yJ31ax00IavOwq
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: --no-verbose
iD8DBQFBUyoJl2ODWuqVSBMRAvjvAJ9cLCYpRM/lX9iyLkm/MjkPWat54gCcC0o1
oBtjDYpsGPI5Eo8Gp4u1ffw=
=a08A
-----END PGP SIGNATURE-----
--U5yJ31ax00IavOwq--
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]