From: michael <trimarchi@gandalf.sssup.it>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH] USB style patch
Date: Wed, 26 Nov 2008 14:18:59 +0100 [thread overview]
Message-ID: <492D4CC3.9020107@gandalf.sssup.it> (raw)
In-Reply-To: <20081126120709.53A62834B020@gemini.denx.de>
Wolfgang Denk wrote:
> Dear michael,
>
> In message <492D31AC.2070006@gandalf.sssup.it> you wrote:
>
>>>> - printf(" NOTE: this command is obsolete and will be phased out\n");
>>>> - printf(" please use 'usb storage' for USB storage devices information\n\n");
>>>> + printf(" NOTE: this command is obsolete and will be"
>>>> + " phased out\n");
>>>> + printf(" please use 'usb storage' for USB storage devices"
>>>> + " information\n\n");
>>>>
>>>>
>>> I believe it is good to keep line lengths below 80 characters in
>>> general, but code should not become less readable by this.
>>> In case of printf lines, it becomes more difficult to 'grep' for the
>>> strings printed in the terminal to find them back in the code.
>>> So, I am very curious about the point of view Wolfgang about this
>>> rule. (How strict does this rule need to be applied?)
>>>
>>>
>> I prefer to break the line but I wait for Walfgang answer.
>>
>
> I tend to go with Remy here, but tyher eis another (even better)
> option: do what the warning says, and remove the obsolete code.
>
>
At the end, can I break to 80 char and "..remove the obsolete code"?
It is nessary a grep with the full message? There are a lot of situation
when the grep is impossible.
> Best regards,
>
> Wolfgang Denk
>
>
Regards Michael
next prev parent reply other threads:[~2008-11-26 13:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 10:45 [U-Boot] [RFC PATCH] USB style patch Michael Trimarchi
2008-11-26 11:15 ` Remy Bohmer
2008-11-26 11:23 ` michael
2008-11-26 12:07 ` Wolfgang Denk
2008-11-26 13:18 ` michael [this message]
2008-11-26 15:14 ` Wolfgang Denk
2008-11-26 16:24 ` [U-Boot] grep for message (was: USB style patch) Alessandro Rubini
2008-11-27 11:21 ` [U-Boot] grep for message michael
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=492D4CC3.9020107@gandalf.sssup.it \
--to=trimarchi@gandalf.sssup.it \
--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