From: Jon Loeliger <jdl@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] USB Storage, add meaningful return value
Date: Tue, 25 Mar 2008 09:36:35 -0500 [thread overview]
Message-ID: <47E90DF3.1040807@freescale.com> (raw)
In-Reply-To: <20080325143407.GA13187@ld0162-tx32.am.freescale.net>
Scott Wood wrote:
> On Tue, Mar 25, 2008 at 09:23:43AM -0500, Jon Loeliger wrote:
>> What do you think? Wouldn't a policy of _always_ using
>> braces even for single sub-statements have just made this
>> a _correct_ no-brainer from the onset? :-)
>
> Yeah, but it'd be ugly. :-)
Luckily, everyone is entitled to their own wrong opinion. :-)
jdl
next prev parent reply other threads:[~2008-03-25 14:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-24 23:19 [U-Boot-Users] [PATCH] USB Storage, add meaningful return value Aras Vaichas
2008-03-25 0:07 ` Wolfgang Denk
2008-03-25 0:23 ` Jerry Van Baren
2008-03-25 1:09 ` Aras Vaichas
2008-03-25 7:36 ` Markus Klotzbücher
2008-03-26 18:14 ` Markus Klotzbücher
2008-03-25 14:23 ` Jon Loeliger
2008-03-25 14:34 ` Scott Wood
2008-03-25 14:36 ` Jon Loeliger [this message]
2008-03-25 14:40 ` Stefan Roese
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=47E90DF3.1040807@freescale.com \
--to=jdl@freescale.com \
--cc=u-boot@lists.denx.de \
/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