From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: John McNamara <john.mcnamara@intel.com>
Cc: Thomas Monjalon <thomas.monjalon@6wind.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v1] doc: autogenerate nic overview table from ini files
Date: Fri, 1 Jul 2016 09:40:22 +0800 [thread overview]
Message-ID: <20160701014022.GK2831@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <1604656.XReoQ6n0NJ@xps13>
On Thu, Jun 30, 2016 at 08:25:14PM +0200, Thomas Monjalon wrote:
> 2016-06-30 19:03, John McNamara:
> > This patch converts the NIC feature table in the overview doc into a set of
> > ini files and adds some functions into the Sphinx conf.py file to convert them
> > back into an RST table.
> >
> > The reason for doing this is to make it easier for PMD maintainers to update
> > the feature matrix that makes up the table and to avoid frequent and hard to
> > resolve conflicts in doc/guides/nics/overview.rst.
>
> Great idea!
Yes, indeed!
The old formats also make the review hard (due to the long/messy diff).
I was also kidding/wishing before that it'd be great if we could have a
column-based diff file. With your proposal, we don't need it any more :)
--yliu
next prev parent reply other threads:[~2016-07-01 1:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 18:03 John McNamara
2016-06-30 18:03 ` John McNamara
2016-06-30 18:25 ` Thomas Monjalon
2016-07-01 1:40 ` Yuanhan Liu [this message]
2016-07-08 19:52 ` Mcnamara, John
2016-07-17 12:59 ` [dpdk-dev] [PATCH v2] " John McNamara
2016-07-19 13:08 ` Ferruh Yigit
2016-07-29 11:59 ` [dpdk-dev] [PATCH v3] " John McNamara
2016-07-29 12:02 ` Mcnamara, John
2016-08-01 21:37 ` Thomas Monjalon
2016-08-03 14:32 ` Bruce Richardson
2016-08-03 16:44 ` 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=20160701014022.GK2831@yliu-dev.sh.intel.com \
--to=yuanhan.liu@linux.intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--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).