From: Juergen Borleis <jbe@pengutronix.de>
To: barebox@lists.infradead.org
Subject: Re: [PATCH 03/10] devinfo: make the output of "devinfo DEVICE" nicer
Date: Mon, 2 Jun 2014 12:09:59 +0200 [thread overview]
Message-ID: <201406021209.59143.jbe@pengutronix.de> (raw)
In-Reply-To: <CAOpc7mF515rdLsmY7bB+UGhWUfQMr58qotUixjuqiXK-Mdribg@mail.gmail.com>
Hi Holger,
On Monday 02 June 2014 11:23:28 Holger Schurig wrote:
> > But parameters can be changed by the user at run-time (e.g. "prompt>
> > enable=1"), while the remaining info is just readable. That is why we
> > used different characters.
>
> I'm not getting you. Parameters are still changeable after this patch.
>
> Or do you mean " = " vs. ":"? Did you chose " = " by intent, i.e. so
> that you can cut&paste text with the mouse?
Yes. IMHO the "=" was intended as a visible feedback about the alterable
characteristics of these parameters.
Copy&paste isn't possible due to the whitespaces.
jbe
--
Pengutronix e.K. | Juergen Borleis |
Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-06-02 10:10 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 9:07 [PATCH 00/10] miscelleanous beautification patches Holger Schurig
2014-05-30 9:05 ` Holger Schurig
2014-05-30 9:07 ` [PATCH 01/10] drvlist: factor the driver list out of 'devinfo' Holger Schurig
2014-05-30 9:09 ` Holger Schurig
2014-05-30 9:07 ` [PATCH 02/10] devinfo: reduce indentation Holger Schurig
2014-05-30 9:08 ` Holger Schurig
2014-05-30 9:49 ` Antony Pavlov
2014-05-30 9:07 ` [PATCH 03/10] devinfo: make the output of "devinfo DEVICE" nicer Holger Schurig
2014-05-30 9:07 ` Holger Schurig
2014-06-02 8:19 ` Juergen Borleis
2014-06-02 9:23 ` Holger Schurig
2014-06-02 10:09 ` Juergen Borleis [this message]
2014-06-02 10:28 ` Holger Schurig
2014-05-30 9:07 ` [PATCH 04/10] parameters: only show possible enumerations if there are any Holger Schurig
2014-05-30 9:09 ` Holger Schurig
2014-05-30 9:07 ` [PATCH 05/10] net: show enetaddr in lowercase Holger Schurig
2014-05-30 9:07 ` [PATCH 06/10] meminfo: purely cosmetical changes Holger Schurig
2014-05-30 9:43 ` Antony Pavlov
2014-05-30 9:37 ` Holger Schurig
2014-05-30 9:07 ` [PATCH 07/10] misc: upper-case some abbreviations Holger Schurig
2014-05-30 9:07 ` [PATCH 08/10] bootm: beautify output Holger Schurig
2014-05-30 9:06 ` Holger Schurig
2014-05-30 9:07 ` [PATCH 09/10] beautify PHY driver names Holger Schurig
2014-05-30 9:17 ` Alexander Aring
2014-05-30 9:30 ` Holger Schurig
2014-05-30 10:03 ` Alexander Aring
2014-06-02 6:59 ` Sascha Hauer
2014-05-30 9:07 ` [PATCH 10/10] device drivers: harmonize underscore in " Holger Schurig
2014-06-02 7:16 ` Sascha Hauer
2014-06-02 7:21 ` [PATCH 00/10] miscelleanous beautification patches Sascha Hauer
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=201406021209.59143.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=barebox@lists.infradead.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 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.