lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sat, 15 Apr 2017 10:59:03 +0200
From:   Jiri Pirko <jiri@...nulli.us>
To:     Stephen Hemminger <stephen@...workplumber.org>
Cc:     netdev@...r.kernel.org, davem@...emloft.net, arkadis@...lanox.com,
        idosch@...lanox.com, mlxsw@...lanox.com, jhs@...atatu.com,
        ivecera@...hat.com, roopa@...ulusnetworks.com,
        f.fainelli@...il.com, vivien.didelot@...oirfairelinux.com,
        john.fastabend@...il.com, andrew@...n.ch,
        simon.horman@...ronome.com
Subject: Re: [patch iproute2/net-next repost] devlink: Add support for
 pipeline debug (dpipe)

Sat, Apr 15, 2017 at 01:01:38AM CEST, stephen@...workplumber.org wrote:
>On Thu, 13 Apr 2017 11:30:27 +0200
>Jiri Pirko <jiri@...nulli.us> wrote:
>
>> We actually took this code from teamdctl (at least it was an influence).
>> Devlink style is so much different in every aspect from the rest of the
>> iproute2 suite. And I did it on purpose, because it is much nicer and
>> easier to read. I would like to continue on this and don't do things in
>> the was the existing tools do. I don't see any problem with that.
>
>No. That is road to ruin. Every package is free to use what ever style
>it wants. But don't crossover please.

So we are stuck with some ugly way just because some other util does it?
Well, in devlink I wrote lot of things differently, nicer. For example
cmdline parsing. Why is it a "road to ruin"?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ