From: Thomas Monjalon <thomas@monjalon.net>
To: Vipin Varghese <vipin.varghese@intel.com>
Cc: dev@dpdk.org, john.mcnamara@intel.com, marko.kovacevic@intel.com,
ferruh.yigit@intel.com, sanjay.padubidri@intel.com,
amol.patel@intel.com, bruce.richardson@intel.com
Subject: Re: [PATCH v5] doc/patches: add meson build to contributing guide
Date: Tue, 12 Feb 2019 10:36:29 +0100 [thread overview]
Message-ID: <7524951.pvg4nOelVy@xps> (raw)
In-Reply-To: <20190129101036.35002-1-vipin.varghese@intel.com>
29/01/2019 11:10, Vipin Varghese:
> +Meson system
> +~~~~~~~~~~~~
What do you think about adding "Makefile system" title for previous section?
We could also add an introduction explaining that both systems must be tested.
> +
> +Compilation of patches is to be tested with ``devtools/test-meson-builds.sh`` script in ``devtools``
A dot is missing. You may remove "in ``devtools``" as it is already in the path.
> +
> +The script internally checks for dependencies, then builds for several
> +combinations of compilation configuration.
> +
next prev parent reply other threads:[~2019-02-12 9:36 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 4:56 [PATCH v1] doc: add meson build to contributing guide Vipin Varghese
2018-10-30 10:54 ` Bruce Richardson
2018-10-30 14:13 ` [PATCH v2] " Vipin Varghese
2018-10-30 14:18 ` [PATCH v3] " Vipin Varghese
2018-11-14 14:30 ` Kovacevic, Marko
2018-11-24 18:57 ` Thomas Monjalon
2019-01-10 16:37 ` Varghese, Vipin
2019-01-24 23:05 ` [PATCH v4] doc/patches: " Vipin Varghese
2019-01-28 0:39 ` Thomas Monjalon
2019-01-28 14:27 ` Varghese, Vipin
2019-01-28 14:52 ` Thomas Monjalon
2019-01-28 15:40 ` Varghese, Vipin
2019-01-29 10:10 ` [PATCH v5] " Vipin Varghese
2019-02-12 9:36 ` Thomas Monjalon [this message]
2019-02-13 5:38 ` Varghese, Vipin
2019-02-13 5:41 ` [PATCH v6] " Vipin Varghese
2019-02-25 17:12 ` [PATCH v7 0/2] guide to debug and troubleshoot Vipin Varghese
2019-02-25 17:12 ` [PATCH v7 1/2] doc: add svg for debug and troubleshoot guide Vipin Varghese
2019-04-01 14:56 ` Mcnamara, John
2019-02-25 17:12 ` [PATCH v7 2/2] doc: add guide for debug and troubleshoot Vipin Varghese
2019-04-01 14:56 ` Mcnamara, John
2019-04-05 8:49 ` [dpdk-dev] " Thomas Monjalon
2019-04-08 3:18 ` Varghese, Vipin
2019-04-08 6:45 ` Thomas Monjalon
2019-04-09 6:33 ` Varghese, Vipin
2019-04-09 6:33 ` [dpdk-dev] [PATCH v8 0/2] guide to " Vipin Varghese
2019-04-09 6:33 ` [dpdk-dev] [PATCH v8 1/2] doc: add svg for debug and troubleshoot guide Vipin Varghese
2019-04-09 6:33 ` [dpdk-dev] [PATCH v8 2/2] doc: add guide for debug and troubleshoot Vipin Varghese
2019-05-04 22:26 ` [dpdk-dev] [PATCH v8 0/2] guide to " Thomas Monjalon
2019-04-01 4:08 ` [PATCH v7 " Varghese, Vipin
2019-02-27 11:41 ` [PATCH v6] doc/patches: add meson build to contributing guide Thomas Monjalon
2019-02-27 12:13 ` Varghese, Vipin
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=7524951.pvg4nOelVy@xps \
--to=thomas@monjalon.net \
--cc=amol.patel@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=sanjay.padubidri@intel.com \
--cc=vipin.varghese@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.