netdev - Re: iproute2 DDMMYY versioning

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]

Message-ID: <20200731082115.5f96a249@hermes.lan>
Date:   Fri, 31 Jul 2020 08:21:15 -0700
From:   Stephen Hemminger <stephen@...workplumber.org>
To:     Or Gerlitz <gerlitz.or@...il.com>
Cc:     Linux Netdev List <netdev@...r.kernel.org>
Subject: Re: iproute2 DDMMYY versioning - why?

On Fri, 31 Jul 2020 16:23:06 +0300
Or Gerlitz <gerlitz.or@...il.com> wrote:

> On Tue, Jul 28, 2020 at 10:51 PM Stephen Hemminger
> <stephen@...workplumber.org> wrote:
> 
> > It is only an historical leftover, because 15 yrs ago that is how Alexy did it  
> 
> So how about putting behind the burden created by this historical leftover
> and moving to use the kernel releases as the emitted version?

The only downside to kernel versioning is the distros will think
"can't use v5.10 because our kernel is still v4.3" and then want
LTS versions of iproute2 which would create significant resource efforts.

Open to changing to kernel versions, it would be trivial to do.
The tagging and releases are by kernel version.
The SNAPSHOT.h is autogenerated by a script, that can be changed.