From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] pkg-utils: describe the case conversion macros in more detail.
Date: Thu, 16 Oct 2014 19:04:40 +0200 [thread overview]
Message-ID: <20141016190440.1191df3a@free-electrons.com> (raw)
In-Reply-To: <1413278627-8504-1-git-send-email-arnout@mind.be>
Dear Arnout Vandecappelle (Essensium/Mind),
On Tue, 14 Oct 2014 11:23:47 +0200, Arnout Vandecappelle
(Essensium/Mind) wrote:
> After the refactoring of the case conversion macros in dd5e620ac, the
> macro became even harder to understand. Improve this explanation a
> little so future generations can make sense of what we're doing here.
>
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> Cc: Thomas De Schampheleire <patrickdepinguin@gmail.com>
Applied, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-10-16 17:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 9:23 [Buildroot] [PATCH] pkg-utils: describe the case conversion macros in more detail Arnout Vandecappelle
2014-10-14 14:45 ` Yann E. MORIN
2014-10-16 17:04 ` Thomas Petazzoni [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=20141016190440.1191df3a@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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