DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
	"Richardson, Bruce" <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 2/3] version: adjust printing for new version	scheme
Date: Wed, 10 Feb 2016 14:28:27 +0000	[thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE202451201@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <7956038.7RoB3127Jy@xps13>

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Monday, December 28, 2015 10:25 PM
> To: Richardson, Bruce <bruce.richardson@intel.com>
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH 2/3] version: adjust printing for new
> version scheme
> 
> 2015-12-21 13:26, Bruce Richardson:
> > Since we are now using a year-month numbering scheme, adjust the
> > printing of the version to always use 2-digits for YY.MM format.

Hi,

In the interest of getting the version patch in and the release notes renamed
I'm going to drop this part of the patchset and resubmit 1/3 and 3/3. If we 
want to rework the version output we can do it in a separate patch.

I am going to maintain the zero padding of the month so that it appear as 16.04
and not 16.4 in "make showversion" and rte_version().

> Shouldn't we take the opportunity to update RTE_VER_PREFIX from "RTE" to
> "DPDK"?

I'm also going to make this change "en passant" since it makes sense and is
in the same file. The version outputs now look like this:

    $ make showversion
    16.04.0-rc0

    RTE>> version_autotest
    Version string: 'DPDK 16.04.0-rc0'

Note, if the s/RTE/DPDK/ change breaks anyone's parsing of output for tests
or otherwise, let me know.

John.
-- 

  reply	other threads:[~2016-02-10 14:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-21 13:26 [dpdk-dev] [PATCH 0/3] switch to using YY.MM version numbers Bruce Richardson
2015-12-21 13:26 ` [dpdk-dev] [PATCH 1/3] version: switch to year/month " Bruce Richardson
2016-02-10 14:33   ` [dpdk-dev] [PATCH v2 1/2] " John McNamara
2016-02-10 14:33     ` [dpdk-dev] [PATCH v2 2/2] doc: rename release notes 2.3 to 16.04 John McNamara
2016-02-10 15:11     ` [dpdk-dev] [PATCH v2 1/2] version: switch to year/month version numbers Thomas Monjalon
2016-02-10 15:31       ` Bruce Richardson
2016-02-10 16:52       ` Mcnamara, John
2015-12-21 13:26 ` [dpdk-dev] [PATCH 2/3] version: adjust printing for new version scheme Bruce Richardson
2015-12-28 22:25   ` Thomas Monjalon
2016-02-10 14:28     ` Mcnamara, John [this message]
2015-12-21 13:26 ` [dpdk-dev] [PATCH 3/3] doc: rename release 2.3 to 16.04 Bruce Richardson
2016-02-10 17:02 ` [dpdk-dev] [PATCH v3 1/2] version: switch to year/month version numbers John McNamara
2016-02-10 17:02   ` [dpdk-dev] [PATCH v3 2/2] doc: rename release notes 2.3 to 16.04 John McNamara
2016-02-10 17:11   ` [dpdk-dev] [PATCH v3 1/2] version: switch to year/month version numbers Mcnamara, John
2016-02-10 17:20     ` Thomas Monjalon
2016-02-10 21:49   ` Thomas Monjalon

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=B27915DBBA3421428155699D51E4CFE202451201@IRSMSX103.ger.corp.intel.com \
    --to=john.mcnamara@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@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).