From: Quentin Monnet <quentin.monnet@6wind.com>
To: Jamal Hadi Salim <hadi@mojatatu.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: Vincent Jardin <vincent.jardin@6wind.com>, netdev@vger.kernel.org
Subject: iproute2: bash completion function for tc
Date: Tue, 26 Apr 2016 09:28:17 +0200 [thread overview]
Message-ID: <571F1891.1030004@6wind.com> (raw)
Hi Jamal, Stephen,
I searched for a function providing auto-completion for `tc` utility in
bash, but I found none. So I have created one, and I would like share it
with the community. It is available here:
https://github.com/6WIND/tc_bash-completion/blob/master/tc
I would like to make it easily available to tc users, so here is a
twofold request:
* I do not know where to submit the code. Should I submit here on netdev
for inclusion in iproute2 package, or rather to the bash-completion
repository on GitHub? I feel like it would receive better feedback and
updates if pushed to iproute2. Could you please provide some advice here?
* The completion for `tc` seems to work well; I have tested it with many
commands, but I am no tc expert, and there are probably some cases where
the completion fails to propose the correct choices. I would be really
interested in any feedback/bug reports that you, or anyone on this list
who uses tc, could provide.
Best regards,
Quentin
next reply other threads:[~2016-04-26 7:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 7:28 Quentin Monnet [this message]
2016-04-28 3:19 ` iproute2: bash completion function for tc Alexei Starovoitov
2016-04-28 5:13 ` Stephen Hemminger
2016-04-28 12:15 ` Quentin Monnet
2016-04-28 16:53 ` Alexei Starovoitov
2016-04-29 8:27 ` [PATCH iproute2] tc: add bash-completion function Quentin Monnet
2016-05-02 22:14 ` Stephen Hemminger
2016-05-03 7:39 ` [PATCH iproute2 v2] " Quentin Monnet
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=571F1891.1030004@6wind.com \
--to=quentin.monnet@6wind.com \
--cc=hadi@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=vincent.jardin@6wind.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;
as well as URLs for NNTP newsgroup(s).