[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20241106152244.21a1c384@hermes.local>
Date: Wed, 6 Nov 2024 15:22:44 -0800
From: Stephen Hemminger <stephen@...workplumber.org>
To: Bjarni Ingi Gislason <bjarniig@...net.is>
Cc: netdev@...r.kernel.org
Subject: Re: dcb.8: some remarks and editorial changes for this manual
On Sun, 3 Nov 2024 01:27:16 +0000
Bjarni Ingi Gislason <bjarniig@...net.is> wrote:
> The man page is from Debian:
>
> Package: iproute2
> Version: 6.11.0-1
> Severity: minor
> Tags: patch
>
> Improve the layout of the man page according to the "man-page(7)"
> guidelines, the output of "mandoc -lint T", the output of
> "groff -mandoc -t -ww -b -z", that of a shell script, and typographical
> conventions.
>
> -.-
>
> Signed-off-by: Bjarni Ingi Gislason <bjarniig@...net.is>
>
> diff --git a/dcb.8 b/dcb.8.new
> index a1d6505..2202224 100644
> --- a/dcb.8
> +++ b/dcb.8.new
> @@ -2,74 +2,74 @@
The format of these patches does not allow for simple application to
the iproute tree. Patches should be on the same file. All your patches
have .new which won't work.
The simplest way to handle this would be:
- take a git branch on your local repo
- do the work there and commit each change
- when ready to:
$ git send-email --subject-prefix 'PATCH v2 iproute' --cover-letter main
A normal patch looks like this one.
diff --git a/MAINTAINERS b/MAINTAINERS
index 1b49d69e..84931abd 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -30,6 +30,7 @@ M: Roopa Prabhu <roopa@...dia.com>
M: Nikolay Aleksandrov <razor@...ckwall.org>
L: bridge@...ts.linux-foundation.org (moderated for non-subscribers)
F: bridge/*
+F: ip/iplink_bridge*
Data Center Bridging - dcb
M: Petr Machata <me@...chata.org>
--
Powered by blists - more mailing lists