netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Locke <kevin@kevinlocke.name>
To: Jesse Brandeburg <jesse.brandeburg@intel.com>
Cc: "John W. Linville" <linville@tuxdriver.com>, netdev@vger.kernel.org
Subject: Re: [PATCH] ethtool: Add bash-completion script
Date: Thu, 11 Apr 2019 10:47:04 -0600	[thread overview]
Message-ID: <20190411164703.GA5716@kevinolos> (raw)
In-Reply-To: <20190411091438.00007a81@intel.com>

On Thu, 2019-04-11 at 09:14 -0700, Jesse Brandeburg wrote:
> On Sun, 7 Apr 2019 20:19:37 -0600 Kevin Locke <kevin@kevinlocke.name> wrote:
>> To aid users constructing a valid ethtool invocation, create a
>> [bash-completion] script to provide [programmable completion] of ethtool
>> arguments.  It supports all current command options.
>> 
>> The script is placed in shell-completion/bash and installed to
>> completionsdir from pkg-config for bash-completion, similar to [kmod].
>> It requires pkg-config 0.18 or later to be installed on the build
>> system which runs aclocal (for the PKG_CHECK_MODULES m4 macro).
>> 
>> [...]
> 
> Thank you! I think this is super useful, and I agree FWIW that it
> should be part of ethtool.  I suspect that it needs to be installed by
> any package manager as part of ethtool install, into the right
> directory.  Could be a followup patch?

Great!  Glad to hear it.  Patched configure.ac and Makefile.am install
the script to `pkg-config --variable=completionsdir bash-completion`
(with fallback to $datadir/bash-completion/completions) by default.
It can be disabled by passing --without-bash-completion-dir or
overridden by --with-bash-completion-dir=$anypath.  I would expect
most distribution packages would install it by default, but if there
are followup patches (for ethtool or to the distributions), I'd be
happy to submit those as well.

> And the only (minor) complaint I have about your patch is that the
> commit message doesn't show how to install it (basically just copy
> ethtool file from this patch to
> f.e. /usr/share/bash-completion/completions/)

Good point.  I will document the install process and the configure
arguments mentioned above and send an updated patch shortly.

> I did a quick touch test of it and it seemed to be completing ethtool
> commands which made me really happy, especially the network interface
> names which are so long.
> 
> Reviewed-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
> 
> And now I'm going to go and tell everyone I work with about this
> patch. :-)

Wonderful!  I'm very glad to hear that you found it useful and I hope
your colleagues appreciate it as well.  Let me know if you or they
find any improvements that I can include in a future version of the
patch.

Thanks for taking the time to review it!

Best,
Kevin

  reply	other threads:[~2019-04-11 16:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-08  2:19 [PATCH] ethtool: Add bash-completion script Kevin Locke
2019-04-11 16:14 ` Jesse Brandeburg
2019-04-11 16:47   ` Kevin Locke [this message]
2019-04-11 17:39 ` [PATCH v2] " Kevin Locke
2019-04-16 18:37   ` John W. Linville
2019-04-17  2:53     ` Kevin Locke
2019-04-18 16:05       ` John W. Linville
2019-04-20  0:16   ` [PATCH v3] " Kevin Locke
2019-04-24 19:54     ` John W. Linville

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=20190411164703.GA5716@kevinolos \
    --to=kevin@kevinlocke.name \
    --cc=jesse.brandeburg@intel.com \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).