From: David Ahern <dsa@cumulusnetworks.com>
To: "Ville Skyttä" <ville.skytta@iki.fi>, "Albino B Neto" <bino@bino.us>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] man: Syntax and warning fixes
Date: Sat, 7 Nov 2015 09:40:47 -0700 [thread overview]
Message-ID: <563E298F.4070200@cumulusnetworks.com> (raw)
In-Reply-To: <CABr9L5B67DkOv8hY7eqogUxrcX+MaaYT3KKtM1W_V5eYpzPpXQ@mail.gmail.com>
On 11/7/15 2:55 AM, Ville Skyttä wrote:
> On Sat, Nov 7, 2015 at 11:47 AM, Albino B Neto <bino@bino.us> wrote:
>> 2015-11-07 7:44 GMT-02:00 Ville Skyttä <ville.skytta@iki.fi>:
>>> ---
>>> man/man8/tc-bpf.8 | 2 +-
>>> man/man8/tipc-bearer.8 | 4 ++--
>>> man/man8/tipc-link.8 | 6 +++---
>>> man/man8/tipc-media.8 | 4 ++--
>>> man/man8/tipc-nametable.8 | 4 ++--
>>> man/man8/tipc-node.8 | 4 ++--
>>> man/man8/tipc-socket.8 | 4 ++--
>>> 7 files changed, 14 insertions(+), 14 deletions(-)
>>>
>>> diff --git a/man/man8/tc-bpf.8 b/man/man8/tc-bpf.8
>>> index 2c02ab2..f5201d3 100644
>>> --- a/man/man8/tc-bpf.8
>>> +++ b/man/man8/tc-bpf.8
>>> @@ -844,7 +844,7 @@ result in the default classid:
>>> Basically, such a minimal generator is equivalent to:
>>
>> Signed-off-by and description ?
>
> Superseding patches sent separately. I suggest documenting the
> requirement for Signed-off-by somewhere (README.devel?); git log shows
> lots of commits without it, especially a bunch of man page related
> ones about a week ago.
I believe man page changes should cc linux-man@vger.kernel.org
next prev parent reply other threads:[~2015-11-07 16:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-07 9:44 [PATCH] man: Syntax and warning fixes Ville Skyttä
2015-11-07 9:47 ` Albino B Neto
2015-11-07 9:55 ` Ville Skyttä
2015-11-07 16:40 ` David Ahern [this message]
2015-11-09 8:51 ` Daniel Borkmann
2015-11-09 9:40 ` Albino B Neto
2015-11-10 7:56 ` Ville Skyttä
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=563E298F.4070200@cumulusnetworks.com \
--to=dsa@cumulusnetworks.com \
--cc=bino@bino.us \
--cc=netdev@vger.kernel.org \
--cc=ville.skytta@iki.fi \
/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).