From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] commands: rename "gpiolib" -> "gpioinfo"
Date: Thu, 15 May 2014 14:52:13 +0200 [thread overview]
Message-ID: <5374B87D.3000501@gmail.com> (raw)
In-Reply-To: <20140515124006.GJ5858@pengutronix.de>
On 05/15/2014 02:40 PM, Sascha Hauer wrote:
> On Thu, May 15, 2014 at 11:20:27AM +0200, Sebastian Hesselbarth wrote:
>> On 05/15/2014 11:08 AM, Holger Schurig wrote:
>>> Signed-off-by: Holger Schurig <holgerschurig@gmail.com>
>>
>> Subject: rename "gpiolib" -> "gpioinfo"
>>
>> How about joining the gpio related commands to "gpio"
>> and use e.g. -l for list?
>
> Which commands do you mean? gpio_direction_output / gpio_set_value
> and friends? I wouldn't change these as we would end up with four
> single letter options (for direction_output, set_value, direction_input,
> get_value) which are hard to memorize.
Maybe I was just irritated by the simple rename of gpiolib to
gpioinfo - which could also be gpiolist or gpio_info to match
the other gpio friends.
Just the first idea that came into my mind when I saw a patch
for the rename - no show-stopper of course.
Sebastian
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-05-15 12:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 9:08 [PATCH] commands: rename "gpiolib" -> "gpioinfo" Holger Schurig
2014-05-15 9:08 ` [PATCH] magicvars: can now also list values Holger Schurig
2014-05-15 9:08 ` Holger Schurig
2014-05-15 9:20 ` [PATCH] commands: rename "gpiolib" -> "gpioinfo" Sebastian Hesselbarth
2014-05-15 9:49 ` Holger Schurig
2014-05-15 12:40 ` Sascha Hauer
2014-05-15 12:52 ` Sebastian Hesselbarth [this message]
2014-05-15 13:01 ` 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=5374B87D.3000501@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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 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.