From: Christopher Li <sparse@chrisli.org>
To: Bernd Petrovitsch <bernd@sysprog.at>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [[PATCH]] Fix a typo - "typdef" is neither C nor plain English
Date: Fri, 20 Aug 2010 12:09:24 -0700 [thread overview]
Message-ID: <AANLkTinLMp_Fm7EByMj2W6hkPhQocVn5paFhmB7EOo56@mail.gmail.com> (raw)
In-Reply-To: <1282304949.10440.234.camel@thorin>
On Fri, Aug 20, 2010 at 3:36 AM, Bernd Petrovitsch <bernd@sysprog.at> wrote:
> - "[typdef]", "[structof]", "[unionof]", "[enum]",
> + "[typedef]", "[structof]", "[unionof]", "[enum]",
Good catch. I will apply it.
Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-08-20 19:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-20 10:36 [[PATCH]] Fix a typo - "typdef" is neither C nor plain English Bernd Petrovitsch
2010-08-20 19:09 ` Christopher Li [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=AANLkTinLMp_Fm7EByMj2W6hkPhQocVn5paFhmB7EOo56@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=bernd@sysprog.at \
--cc=linux-sparse@vger.kernel.org \
/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 NNTP newsgroup(s).