[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180604110225.GX11363@tatos.vnet>
Date: Mon, 4 Jun 2018 13:02:25 +0200
From: Phil Sutter <psutter@...hat.com>
To: Jesper Dangaard Brouer <brouer@...hat.com>
Cc: Daniel Borkmann <daniel@...earbox.net>,
alexei.starovoitov@...il.com, netdev@...r.kernel.org,
Jakub Kicinski <jakub.kicinski@...ronome.com>,
Jakub Kicinski <kubakici@...pl>,
Quentin Monnet <quentin.monnet@...ronome.com>
Subject: Re: [PATCH bpf-next v3 05/11] bpf: avoid retpoline for
lookup/update/delete calls on maps
Hi!
On Sun, Jun 03, 2018 at 07:08:55PM +0200, Jesper Dangaard Brouer wrote:
[...]
> Secondly I personally *hate* how the 'ip' does it's short options
> parsing and especially order/precedence ambiguity. Phil Sutter
> (Fedora/RHEL iproute2 maintainer) have a funny quiz illustrating the
> ambiguity issues.
Hehe, yes. It's a classical case of something smart evolving into a
pain: At first there's only 'ip link', so you allow 'ip l' as a
shortcut. Then someone implements 'ip l2tp' - so what do you do?
Establish a policy of abbreviation having to be unique and break
existing behaviour or accept the mess and head on.
My suggestion would be to not get into the abbreviated subcommands
business at all but instead ship and maintain a bash-completion script.
Cheers, Phil
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists