netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Or Gerlitz <gerlitz.or@gmail.com>
Cc: Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: iproute2 DDMMYY versioning - why?
Date: Tue, 28 Jul 2020 12:51:36 -0700	[thread overview]
Message-ID: <20200728125136.6c5b46e8@hermes.lan> (raw)
In-Reply-To: <CAJ3xEMhk+EQ_avGSBDB5_Gnj09w3goUJKkxzt8innWvFkTeEVA@mail.gmail.com>

On Tue, 28 Jul 2020 16:05:50 +0300
Or Gerlitz <gerlitz.or@gmail.com> wrote:

> Stephen,
> 
> Taking into account that iproute releases are aligned with the kernel
> ones -- is there any real reason for the confusing DDMMYY double
> versioning?
> 
> I see that even the git tags go after the kernel releases..
> 
> Or.
> 

It is only an historical leftover, because 15 yrs ago that is how Alexy did it


  parent reply	other threads:[~2020-07-28 19:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-28 13:05 iproute2 DDMMYY versioning - why? Or Gerlitz
2020-07-28 18:57 ` Jakub Kicinski
2020-07-28 19:51 ` Stephen Hemminger [this message]
2020-07-31 13:23   ` Or Gerlitz
2020-07-31 15:21     ` Stephen Hemminger
2020-08-01 17:32 ` [RFC] replace SNAPSHOT with auto-generated version Stephen Hemminger

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=20200728125136.6c5b46e8@hermes.lan \
    --to=stephen@networkplumber.org \
    --cc=gerlitz.or@gmail.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).