From: Aaron Conole <aconole@redhat.com>
To: Ali Alnubani <alialnu@nvidia.com>
Cc: <ci@dpdk.org>
Subject: Re: [PATCH 2/2] pw_maintainers_cli: write errors to stderr
Date: Mon, 25 Apr 2022 13:18:58 -0400 [thread overview]
Message-ID: <f7tfsm1m67x.fsf@redhat.com> (raw)
In-Reply-To: <20220415101611.364-2-alialnu@nvidia.com> (Ali Alnubani's message of "Fri, 15 Apr 2022 13:16:11 +0300")
Ali Alnubani <alialnu@nvidia.com> writes:
> Redirect error messages to stderr instead of stdout and
> reword 2 of them.
>
> Signed-off-by: Ali Alnubani <alialnu@nvidia.com>
> ---
I don't see how this is related to previous patch, but it makes sense,
so:
Acked-by: Aaron Conole <aconole@redhat.com>
next prev parent reply other threads:[~2022-04-25 17:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 10:16 [PATCH 1/2] pw_maintainers_cli: try delegating to multiple maintainers Ali Alnubani
2022-04-15 10:16 ` [PATCH 2/2] pw_maintainers_cli: write errors to stderr Ali Alnubani
2022-04-25 17:18 ` Aaron Conole [this message]
2022-04-26 9:28 ` Ali Alnubani
2022-04-25 17:18 ` [PATCH 1/2] pw_maintainers_cli: try delegating to multiple maintainers Aaron Conole
2022-05-02 16:47 ` 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=f7tfsm1m67x.fsf@redhat.com \
--to=aconole@redhat.com \
--cc=alialnu@nvidia.com \
--cc=ci@dpdk.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).