From: Stephen Hemminger <stephen@networkplumber•org>
To: Andrea Claudi <aclaudi@redhat•com>
Cc: netdev@vger•kernel.org, Leon Romanovsky <leon@kernel•org>,
Jiri Pirko <jiri@resnulli•us>, Jon Maloy <jmaloy@redhat•com>,
David Ahern <dsahern@gmail•com>
Subject: Re: [PATCH iproute2 1/2] docs, man: fix some typos
Date: Thu, 11 Jan 2024 09:21:45 -0800 [thread overview]
Message-ID: <20240111092145.7de8c2d0@hermes.local> (raw)
In-Reply-To: <cda844f5f7fe512ca9b7f87a6545157394b9d9ae.1704816744.git.aclaudi@redhat.com>
On Tue, 9 Jan 2024 17:32:34 +0100
Andrea Claudi <aclaudi@redhat•com> wrote:
> Fix some typos and spelling errors in iproute2 documentation.
>
> Signed-off-by: Andrea Claudi <aclaudi@redhat•com>
> ---
> doc/actions/actions-general | 2 +-
> examples/bpf/README | 2 +-
> man/man8/devlink-rate.8 | 2 +-
> tipc/README | 2 +-
> 4 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/doc/actions/actions-general b/doc/actions/actions-general
> index a0074a58..41c74d38 100644
> --- a/doc/actions/actions-general
> +++ b/doc/actions/actions-general
I am thinking about removing all the stuff in doc/actions.
It is in rough shape and doesn't really provide more info than is
available elsewhere. My preference is to have information in only
one place the man pages.
next prev parent reply other threads:[~2024-01-11 17:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 16:32 [PATCH iproute2 0/2] Fix some more typos in docs and comments Andrea Claudi
2024-01-09 16:32 ` [PATCH iproute2 1/2] docs, man: fix some typos Andrea Claudi
2024-01-10 10:35 ` Petr Machata
2024-01-11 17:21 ` Stephen Hemminger [this message]
2024-01-11 19:39 ` Stephen Hemminger
2024-01-09 16:32 ` [PATCH iproute2 2/2] treewide: fix typos in various comments Andrea Claudi
2024-01-10 10:54 ` Petr Machata
2024-01-11 19:40 ` Stephen Hemminger
2024-01-12 11:23 ` Andrea Claudi
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=20240111092145.7de8c2d0@hermes.local \
--to=stephen@networkplumber$(echo .)org \
--cc=aclaudi@redhat$(echo .)com \
--cc=dsahern@gmail$(echo .)com \
--cc=jiri@resnulli$(echo .)us \
--cc=jmaloy@redhat$(echo .)com \
--cc=leon@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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