From: David Marchand <david.marchand@redhat.com>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, roretzla@linux.microsoft.com,
Chengwen Feng <fengchengwen@huawei.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Subject: Re: [PATCH] doc: replace code blocks with includes in logging guide
Date: Wed, 6 Mar 2024 22:10:03 +0100 [thread overview]
Message-ID: <CAJFAV8wODa02GecpiVc7RcVoQdsh+oxTiAK+dL6Ge873wyjWNw@mail.gmail.com> (raw)
In-Reply-To: <20240227142138.1942161-1-david.marchand@redhat.com>
On Tue, Feb 27, 2024 at 3:22 PM David Marchand
<david.marchand@redhat.com> wrote:
>
> Rather than have a block of code as example that gets unaligned as
> time passes, add literal includes.
>
> The coding style guide points at the cfgfile library, let's use it too
> as an example.
>
> Fixes: 97433132c2ed ("lib: use per line logging in helpers")
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
Applied.
--
David Marchand
prev parent reply other threads:[~2024-03-06 21:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 14:21 David Marchand
2024-03-06 21:10 ` David Marchand [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=CAJFAV8wODa02GecpiVc7RcVoQdsh+oxTiAK+dL6Ge873wyjWNw@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=roretzla@linux.microsoft.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).