netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Bjarni Ingi Gislason <bjarniig@simnet.is>
Cc: netdev@vger.kernel.org
Subject: Re: dcb.8: some remarks and editorial changes for this manual
Date: Wed, 6 Nov 2024 15:22:44 -0800	[thread overview]
Message-ID: <20241106152244.21a1c384@hermes.local> (raw)
In-Reply-To: <ZybRdNeIHWohpWYN@kassi.invalid.is>

On Sun, 3 Nov 2024 01:27:16 +0000
Bjarni Ingi Gislason <bjarniig@simnet.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@simnet.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@nvidia.com>
 M: Nikolay Aleksandrov <razor@blackwall.org>
 L: bridge@lists.linux-foundation.org (moderated for non-subscribers)
 F: bridge/*
+F: ip/iplink_bridge*
 
 Data Center Bridging - dcb
 M: Petr Machata <me@pmachata.org>
-- 

      parent reply	other threads:[~2024-11-06 23:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-03  1:27 dcb.8: some remarks and editorial changes for this manual Bjarni Ingi Gislason
2024-11-03 15:58 ` Stephen Hemminger
2024-11-06 23:22 ` Stephen Hemminger [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=20241106152244.21a1c384@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=bjarniig@simnet.is \
    --cc=netdev@vger.kernel.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).