From: Stephen Hemminger <stephen@networkplumber.org>
To: Luca Boccassi <bluca@debian.org>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 v2 1/4] man: drop references to Debian-specific paths
Date: Sat, 30 Dec 2017 09:44:10 -0800 [thread overview]
Message-ID: <20171230094410.5f839475@xeon-e3> (raw)
In-Reply-To: <20171230103117.27544-1-bluca@debian.org>
On Sat, 30 Dec 2017 11:31:14 +0100
Luca Boccassi <bluca@debian.org> wrote:
> Documentation should be distribution-agnostic - any specific quirks
> should be handled by downstream maintainers, if necessary.
> Remove mentions of Debian paths and package names.
>
> Signed-off-by: Luca Boccassi <bluca@debian.org>
Applied all of these
prev parent reply other threads:[~2017-12-30 17:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-29 22:01 [PATCH iproute2 1/4] man: drop references to Debian-specific paths Luca Boccassi
2017-12-29 22:01 ` [PATCH iproute2 2/4] man: add more keywords to ip.8 short description Luca Boccassi
2017-12-30 4:02 ` Stephen Hemminger
2017-12-30 10:32 ` Luca Boccassi
2017-12-29 22:01 ` [PATCH iproute2 3/4] man: ip-address: document 15-char limit for LABEL Luca Boccassi
2017-12-30 4:04 ` Stephen Hemminger
2017-12-30 10:32 ` Luca Boccassi
2017-12-29 22:01 ` [PATCH iproute2 4/4] man: routel/routef: don't mention filesystem paths Luca Boccassi
2017-12-30 4:05 ` Stephen Hemminger
2017-12-30 10:31 ` [PATCH iproute2 v2 1/4] man: drop references to Debian-specific paths Luca Boccassi
2017-12-30 10:31 ` [PATCH iproute2 v2 2/4] man: add more keywords to ip.8 short description Luca Boccassi
2017-12-30 10:31 ` [PATCH iproute2 v2 3/4] man: ip-address: document 15-char limit for LABEL Luca Boccassi
2017-12-30 10:31 ` [PATCH iproute2 v2 4/4] man: routel/routef: don't mention filesystem paths Luca Boccassi
2017-12-30 17:44 ` 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=20171230094410.5f839475@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=bluca@debian.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.