Linux IEEE 802.15.4 and 6LoWPAN development
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Stefan Schmidt <s.schmidt@samsung.com>
Cc: linux-wpan@vger.kernel.org
Subject: Re: [PATCH wpan-tools 1/2] treewide: shorten commands
Date: Tue, 20 Jan 2015 12:47:18 +0100	[thread overview]
Message-ID: <20150120114717.GC3922@omega> (raw)
In-Reply-To: <20150120113231.GA3922@omega>

On Tue, Jan 20, 2015 at 12:32:31PM +0100, Alexander Aring wrote:
> On Tue, Jan 20, 2015 at 11:05:26AM +0000, Stefan Schmidt wrote:
> > Hello.
> > 
> > On 20/01/15 11:35, Alexander Aring wrote:
> > >This patch shorten all commands. I had the idea to make a similarity
> > >from PIB/MIB values according the 802.15.4 names convention but this is
> > >bad for fast shell hacking. Mainly I remove the underscore and some
> > >additional information which are not necessary like "_addr" in
> > >"short_addr" and "extended_addr" and such things.
> > >
> > >Signed-off-by: Alexander Aring <alex.aring@gmail.com>
> > >---
> > >  src/info.c      | 10 +++++-----
> > >  src/interface.c | 20 ++++++++++----------
> > >  src/mac.c       | 10 +++++-----
> > >  src/phy.c       |  6 +++---
> > >  4 files changed, 23 insertions(+), 23 deletions(-)
> > 
> > Hmm, it feels like you are going overboard with shorting things here. Why is
> > the reason behind it? Just less typing? Shell auto completion would handle
> > this. :)
> > 
> 
> it's just less typing and I notice that the original iw command doesn't
> have an underscore in their commands.
> 
> The first time when I hacked it, then I just took the same naming
> convention in kernel implementation which use the naming convention from
> 802.15.4 standard (without the beginning "MAC" and "PHY" keywords). Now
> I am too lazy to always type pan_id short_addr, etc...
> 
> Do you like to implement some completion stuff which can be shipped out
> optionally with the wpan-tools? :-)
> 
> > I mean it is up to you but with this you might break scripts that are
> > already out there and I think the current  commands are quite fine. Cutting
> > out the underscores makes some of these hard to read imho.
> > 
> 
> mhhh, I am unsure also about this and just gave it a try if somebody
> screams I would maybe reconsider this patch. :-)
> 

ok. I will drop this patch. Will resend the second patch later.

- Alex

  reply	other threads:[~2015-01-20 11:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-20 10:35 [PATCH wpan-tools 1/2] treewide: shorten commands Alexander Aring
2015-01-20 10:35 ` [PATCH wpan-tools 2/2] interface: remove twice phy information Alexander Aring
2015-01-20 11:05 ` [PATCH wpan-tools 1/2] treewide: shorten commands Stefan Schmidt
2015-01-20 11:32   ` Alexander Aring
2015-01-20 11:47     ` Alexander Aring [this message]
2015-01-20 14:43     ` Stefan Schmidt

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=20150120114717.GC3922@omega \
    --to=alex.aring@gmail.com \
    --cc=linux-wpan@vger.kernel.org \
    --cc=s.schmidt@samsung.com \
    /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