From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: Jesse Brandeburg <jesse.brandeburg@intel.com>
Cc: <ben@decadent.org.uk>, <netdev@vger.kernel.org>, <bwh@kernel.org>
Subject: Re: [PATCH v1] ethtool: properly indent man sub-options
Date: Thu, 28 Jan 2016 09:18:28 -0800 [thread overview]
Message-ID: <20160128091828.0000497e@unknown> (raw)
In-Reply-To: <1452217843-18254-1-git-send-email-jesse.brandeburg@intel.com>
On Thu, 7 Jan 2016 17:50:43 -0800
Jesse Brandeburg <jesse.brandeburg@intel.com> wrote:
> The ethtool.8 file was full of lots of incorrectly indented
> bits. This fixes the arguments to options to be indented in
> a visually appealing way.
Hey Ben (ethtool maintainer), I never saw a response to this patch, do
I need to resend it?
next prev parent reply other threads:[~2016-01-28 17:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 1:50 [PATCH v1] ethtool: properly indent man sub-options Jesse Brandeburg
2016-01-28 17:18 ` Jesse Brandeburg [this message]
2016-01-29 7:45 ` Jeff Kirsher
2016-03-13 16:06 ` Ben Hutchings
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=20160128091828.0000497e@unknown \
--to=jesse.brandeburg@intel.com \
--cc=ben@decadent.org.uk \
--cc=bwh@kernel.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 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).