From: Thomas Monjalon <thomas@monjalon.net>
To: "Walsh, Conor" <conor.walsh@intel.com>,
"Fogarty, Conor" <conor.fogarty@intel.com>
Cc: "david.marchand@redhat.com" <david.marchand@redhat.com>,
"olivier.matz@6wind.com" <olivier.matz@6wind.com>,
"Iremonger, Bernard" <bernard.iremonger@intel.com>,
"orika@nvidia.com" <orika@nvidia.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"Kantecki, Tomasz" <tomasz.kantecki@intel.com>,
"skori@marvell.com" <skori@marvell.com>,
"pbhagavatula@marvell.com" <pbhagavatula@marvell.com>,
"jerinj@marvell.com" <jerinj@marvell.com>,
"kirankumark@marvell.com" <kirankumark@marvell.com>,
"ndabilpuram@marvell.com" <ndabilpuram@marvell.com>,
"Hunt, David" <david.hunt@intel.com>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>,
"Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
"Singh, Jasvinder" <jasvinder.singh@intel.com>,
"Marohn, Byron" <byron.marohn@intel.com>,
"Wang, Yipeng1" <yipeng1.wang@intel.com>,
"Van Haaren, Harry" <harry.van.haaren@intel.com>,
"rsanford@akamai.com" <rsanford@akamai.com>,
"Carrillo, Erik G" <erik.g.carrillo@intel.com>,
"Doherty, Declan" <declan.doherty@intel.com>,
"Rybalchenko, Kirill" <kirill.rybalchenko@intel.com>,
dev@dpdk.org, "Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] doc/sample_app_ug: use code snippets in sample app guides
Date: Sat, 31 Jul 2021 15:46:51 +0200 [thread overview]
Message-ID: <1750653.er4E50BqMo@thomas> (raw)
In-Reply-To: <SN6PR11MB3086D84ADB6520417F8597A2FCE99@SN6PR11MB3086.namprd11.prod.outlook.com>
> Currently the sample app user guides use hard coded code snippets,
> this patch changes these to use literalinclude which will dynamically
> update the snippets as changes are made to the code.
> This was introduced in commit 413c75c33c40 ("doc: show how to include
> code in guides"). Comments within the sample apps were updated to
> accommodate this as part of this patch. This will help to ensure that
> the code within the sample app user guides is up to date and not out
> of sync with the actual code.
>
> Signed-off-by: Conor Fogarty <conor.fogarty@intel.com>
> Signed-off-by: Conor Walsh <conor.walsh@intel.com>
> Acked-by: John McNamara <john.mcnamara@intel.com>
Applied, thanks
prev parent reply other threads:[~2021-07-31 13:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 9:58 [dpdk-dev] [PATCH] " Conor Fogarty
2021-07-15 8:28 ` David Marchand
2021-07-16 11:10 ` Walsh, Conor
2021-07-16 13:57 ` [dpdk-dev] [PATCH v2] " Conor Walsh
2021-07-27 10:56 ` Mcnamara, John
2021-07-31 13:46 ` Thomas Monjalon [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=1750653.er4E50BqMo@thomas \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=bruce.richardson@intel.com \
--cc=byron.marohn@intel.com \
--cc=conor.fogarty@intel.com \
--cc=conor.walsh@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=david.hunt@intel.com \
--cc=david.marchand@redhat.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=erik.g.carrillo@intel.com \
--cc=harry.van.haaren@intel.com \
--cc=jasvinder.singh@intel.com \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=kirankumark@marvell.com \
--cc=kirill.rybalchenko@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=ndabilpuram@marvell.com \
--cc=olivier.matz@6wind.com \
--cc=orika@nvidia.com \
--cc=pbhagavatula@marvell.com \
--cc=rsanford@akamai.com \
--cc=skori@marvell.com \
--cc=tomasz.kantecki@intel.com \
--cc=yipeng1.wang@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).