This is the mail archive of the
cygwin-talk
mailing list for the cygwin project.
Re: [PATCH] Re: 1.7 winbase.h (ilockcmpexch) compile error
- From: Dave Korn <dave dot korn dot cygwin at googlemail dot com>
- To: The I Guess The Reference Is Not As Obvious As I Thought But At Least It Is Vulgar Cygwin-Talk Maiming List <cygwin-talk at cygwin dot com>
- Date: Tue, 07 Jul 2009 23:54:59 +0100
- Subject: Re: [PATCH] Re: 1.7 winbase.h (ilockcmpexch) compile error
- References: <Pine.CYG.4.58.0906241239470.2248@PC1163-8460-XP.flightsafety.com> <4A53BC5D.7010401@gmail.com> <20090707213202.GA10393@ednor.casa.cgf.cx> <4A53C441.5090708@gmail.com> <20090707214331.GA10497@ednor.casa.cgf.cx> <4A53C912.8030106@gmail.com> <20090707221534.GA10602@ednor.casa.cgf.cx>
- Reply-to: The Vulgar and Unprofessional Cygwin-Talk List <cygwin-talk at cygwin dot com>
Christopher Faylor wrote:
> On Tue, Jul 07, 2009 at 11:15:46PM +0100, Dave Korn wrote:
>> Christopher Faylor wrote:
>>> On Tue, Jul 07, 2009 at 10:55:13PM +0100, Dave Korn wrote:
>>>> Christopher Faylor wrote:
>>>>> On Tue, Jul 07, 2009 at 10:21:33PM +0100, Dave Korn wrote:
>>>>>> winsup/cygwin/ChangeLog:
>>>>>>
>>>>>> * winbase.h (ilockexch): Avoid making 'ret' volatile.
>>>>>> (ilockcmpexch): Likewise.
>>>>>>
>>>>>> Ok?
>>>>> Yes. Thanks.
>>>> Applied, and I even caught the changelog formatting in time!
>>> I think I may have to turn in my Anal Whitespace Enforcer badge.
>> <weeblandbob> That's no *white* space .... </weeblandbob>
>
> Er, not really. It's just making sure whitespace is correct. For
> instance, if you had no spaces after the colon, then it would have been
> my job to tell you.
<weeblandbob> The space after my colon is brown! </weeblandbob>
cheers,
DaveK