From: Ray Kinsella <mdr@ashroe.eu>
To: "Mcnamara, John" <john.mcnamara@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc: Changes to ABI Policy introducing major ABI versions
Date: Tue, 30 Jul 2019 11:35:37 +0100 [thread overview]
Message-ID: <a166c003-f3de-26dd-e865-6d67548114cd@ashroe.eu> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE24BCA1841@IRSMSX103.ger.corp.intel.com>
Thanks John,
I will fix it.
Ray K
On 30/07/2019 11:34, Mcnamara, John wrote:
>
>
>> -----Original Message-----
>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Ray Kinsella
>> Sent: Thursday, July 4, 2019 1:27 PM
>> To: dev@dpdk.org
>> Cc: mdr@ashroe.eu
>> Subject: [dpdk-dev] [PATCH] doc: Changes to ABI Policy introducing major
>> ABI versions
>>
>> This policy change introduces major ABI versions, these are declared every
>> two years, typically aligned with the LTS release and are supported by
>> subsequent releases for the next two years.
>> This change is intended to improve ABI stabilty for those projects
>> consuming DPDK.
>>
>
>
>
>> ...
>>
>> +A LTS release may align with the declaration of a new major ABI
>> +version, please read the `DPDK ABI/API policy`_ for more information.
>
> This should be `<DPDK ABI/API policy>`_ to avoid a build warning/error
> since the target contains spaces.
>
> Also, the subject line should be lowercase by convention, apart from acronyms.
>
> $ ./devtools/check-git-log.sh
> Wrong headline uppercase:
> doc: >C<hanges to ABI Policy introducing major ABI versions
>
> Something like:
>
> doc: changes to ABI policy introducing major ABI versions
>
> John
>
>
prev parent reply other threads:[~2019-07-30 10:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-04 12:26 [dpdk-dev] [PATCH] " Ray Kinsella
2019-07-04 12:26 ` [dpdk-dev] [PATCH] doc: " Ray Kinsella
2019-07-30 10:34 ` Mcnamara, John
2019-07-30 10:35 ` Ray Kinsella [this message]
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=a166c003-f3de-26dd-e865-6d67548114cd@ashroe.eu \
--to=mdr@ashroe.eu \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.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).