From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] eal: resort symbols in EXPERIMENTAL section
Date: Fri, 14 Jun 2019 16:39:12 +0900 [thread overview]
Message-ID: <2320193.YWZSPdnyqu@xps> (raw)
In-Reply-To: <20190405203036.27109-1-stephen@networkplumber.org>
06/04/2019 05:30, Stephen Hemminger:
> The symbols in the EXPERIMENTAL were close to alphabetic
> order but running sort showed several mistakes.
>
> This has no impact on code, API, ABI or otherwise.
> Purely for humans.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
I don't think it's worth adding a layer of git history for this sort.
I would prefer to leave it as is.
next prev parent reply other threads:[~2019-06-14 7:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 20:30 Stephen Hemminger
2019-04-05 20:30 ` Stephen Hemminger
2019-06-14 7:39 ` Thomas Monjalon [this message]
2019-06-14 7:44 ` David Marchand
2019-06-14 15:32 ` Ferruh Yigit
2019-06-20 17:23 ` David Marchand
2019-07-26 13:54 ` David Marchand
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=2320193.YWZSPdnyqu@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).