Re: [Patch] cygcheck: Don't use keyeprint if GetLastError is irrelevant.

2004-10-31 Thread Bas van Gompel
Op Sat, 30 Oct 2004 19:42:16 -0400 schreef Christopher Faylor in <[EMAIL PROTECTED]>: : On Sat, Oct 30, 2004 at 11:32:27PM +0200, Bas van Gompel wrote: : > 2004-10-28 Bas van Gompel <[EMAIL PROTECTED]> : > : > * cygcheck.cc (get_dword): Fix errormessage. : > (cygwin_info): Ditto. : >

Re: [Patch] cygcheck: Don't use keyeprint if GetLastError is irrelevant.

2004-10-30 Thread Christopher Faylor
On Sat, Oct 30, 2004 at 11:32:27PM +0200, Bas van Gompel wrote: >2004-10-28 Bas van Gompel <[EMAIL PROTECTED]> > > * cygcheck.cc (get_dword): Fix errormessage. > (cygwin_info): Ditto. > (track_down): Ditto. > (check_keys): Ditto. Go ahead and check these in. Thanks, cgf

Re: [Patch] cygcheck: Don't use keyeprint if GetLastError is irrelevant.

2004-10-30 Thread Bas van Gompel
Op Fri, 29 Oct 2004 11:22:38 -0400 schreef Christopher Faylor in <[EMAIL PROTECTED]>: : On Fri, Oct 29, 2004 at 06:31:11AM +0200, Bas van Gompel wrote: : > Following (trivial, once more, I hope) patch cleans up some of the : > (IMO) inappropriate ``keyeprint'' usage in cygcheck. It (keyeprint) : >

Re: [Patch] cygcheck: Don't use keyeprint if GetLastError is irrelevant.

2004-10-29 Thread Christopher Faylor
On Fri, Oct 29, 2004 at 06:31:11AM +0200, Bas van Gompel wrote: >Following (trivial, once more, I hope) patch cleans up some of the >(IMO) inappropriate ``keyeprint'' usage in cygcheck. It (keyeprint) >should not be used when GetLastError does not apply, I think. Also the >format ending in ``failed

[Patch] cygcheck: Don't use keyeprint if GetLastError is irrelevant.

2004-10-28 Thread Bas van Gompel
Hi, Following (trivial, once more, I hope) patch cleans up some of the (IMO) inappropriate ``keyeprint'' usage in cygcheck. It (keyeprint) should not be used when GetLastError does not apply, I think. Also the format ending in ``failed'' can cause strange messages like ``NULL pointer for file fail