From: Josh Triplett <josh@freedesktop.org>
To: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
Cc: Sparse Mailing-list <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH 3/5] Add (more) support for WIN32 attribute names
Date: Tue, 22 May 2007 15:50:57 -0700 [thread overview]
Message-ID: <465373D1.9060303@freedesktop.org> (raw)
In-Reply-To: <46532FD5.6000307@ramsay1.demon.co.uk>
[-- Attachment #1: Type: text/plain, Size: 961 bytes --]
Ramsay Jones wrote:
> In particular, the following identifiers (along with their __X__ variants)
> are now accepted as attribute names: fastcall, dllimport and dllexport.
> (cdecl and stdcall were added in baf2c5a84e by Michael Stefaniuc).
> For now, at least, these attributes are just ignored.
Your patch seems to have some whitespace damage in the form of extra leading
spaces. I've manually modified it to apply this time, but please figure out
what causes these patches to break and fix it. You may want to test by
sending patches to yourself and trying to apply them. I notice that you use
Thunderbird; format=flowed may cause the problem, so try turning it off by
disabling the preference mailnews.send_plaintext_flowed . You can do so
either via Edit -> Preferences -> Advanced -> Config Editor; alternatively, if
you have Enigmail installed, it offers a checkbox to turn off format=flowed in
its preferneces.
- Josh Triplett
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2007-05-22 22:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-22 18:00 [PATCH 3/5] Add (more) support for WIN32 attribute names Ramsay Jones
2007-05-22 22:50 ` Josh Triplett [this message]
2007-05-24 15:59 ` Ramsay Jones
2007-05-24 17:24 ` Randy Dunlap
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=465373D1.9060303@freedesktop.org \
--to=josh@freedesktop.org \
--cc=linux-sparse@vger.kernel.org \
--cc=ramsay@ramsay1.demon.co.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.