From: james_p_freyensee@linux.intel.com (J Freyensee)
Subject: [PATCH RFC] nvme-cli: propose 'c' vs 'r' for connect flag
Date: Fri, 23 Sep 2016 09:43:24 -0700 [thread overview]
Message-ID: <1474649004.15303.44.camel@linux.intel.com> (raw)
In-Reply-To: <20160923150026.GB19352@keith>
On Fri, 2016-09-23@11:00 -0400, Keith Busch wrote:
> On Thu, Sep 22, 2016@08:33:01PM -0700, Christoph Hellwig wrote:
> >
> > On Thu, Sep 22, 2016@03:37:20PM -0700, Jay Freyensee wrote:
> > >
> > > I am not sure if it matters too much except in possibly
> > > human usage understanding, but '-r' is used in the 'discover'
> > > command for --raw.??Change the --reconnect-delay flag
> > > single letter to something not being used in any fabrics
> > > command.
> >
> > Sounds ok to me.??But I have to say dealing with these short
> > options
> > start to be a little annoying.??For a lot of these commands I'd
> > prefer
> > to simply support long options only if we could (I'll need to look
> > at argconfig.c in a bit more detail how easily that could be done).
>
> Aw, I like having short opts. Yeah, some were arbitrarily picked to
> avoid
> clashes (though I clearly missed some clashes), and difficult to
> remember,
> but every sub-command shows consistent helpful usage info with a "
> --help".
OK, I'll respin this, add the review tags, and remove the RFC and send
it back out.
next prev parent reply other threads:[~2016-09-23 16:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 22:37 [PATCH RFC] nvme-cli: propose 'c' vs 'r' for connect flag Jay Freyensee
2016-09-23 3:33 ` Christoph Hellwig
2016-09-23 14:49 ` Steve Wise
2016-09-23 15:00 ` Keith Busch
2016-09-23 16:43 ` J Freyensee [this message]
2016-09-23 20:59 ` Sagi Grimberg
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=1474649004.15303.44.camel@linux.intel.com \
--to=james_p_freyensee@linux.intel.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