From: Dave Korn <dave.korn.cygwin@googlemail.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@cygwin.com>
Subject: Re: [PATCH] Re: 1.7 winbase.h (ilockcmpexch) compile error
Date: Tue, 07 Jul 2009 22:42:00 -0000 [thread overview]
Message-ID: <4A53D243.70507@gmail.com> (raw)
In-Reply-To: <20090707221534.GA10602@ednor.casa.cgf.cx>
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
prev parent reply other threads:[~2009-07-07 22:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.CYG.4.58.0906241239470.2248@PC1163-8460-XP.flightsafety.com>
[not found] ` <4A53BC5D.7010401@gmail.com>
[not found] ` <20090707213202.GA10393@ednor.casa.cgf.cx>
[not found] ` <4A53C441.5090708@gmail.com>
[not found] ` <20090707214331.GA10497@ednor.casa.cgf.cx>
2009-07-07 22:03 ` Dave Korn
2009-07-07 22:15 ` Christopher Faylor
2009-07-07 22:42 ` Dave Korn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A53D243.70507@gmail.com \
--to=dave.korn.cygwin@googlemail.com \
--cc=cygwin-talk@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).