From: esr@thyrsus.com
To: linux-wireless@vger.kernel.org
Subject: Problems in regulatory.bin.5
Date: Tue, 12 Jun 2018 15:16:14 -0400 (EDT) [thread overview]
Message-ID: <20180612191614.28DC13A4F51@snark.thyrsus.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 708 bytes --]
This is automatically generated email about markup problems in a man
page for which you appear to be responsible. If you are not the right
person or list, please tell me so I can correct my database.
See http://catb.org/~esr/doclifter/bugs.html for details on how and
why these patches were generated. Feel free to email me with any
questions. Note: These patches do not change the modification date of
any manual page. You may wish to do that by hand.
I apologize if this message seems spammy or impersonal. The volume of
markup bugs I am tracking is over five hundred - there is no real
alternative to generating bugmail from a database and template.
--
Eric S. Raymond
[-- Attachment #2: Type: text/plain, Size: 834 bytes --]
Problems with regulatory.bin.5:
.SS markup in name section seriously confuses parsing, and sections
don't follow standard naming conventions.
--- regulatory.bin.5-unpatched 2012-07-02 01:57:14.437776710 -0400
+++ regulatory.bin.5 2012-07-02 01:59:11.117774528 -0400
@@ -2,12 +2,7 @@
.SH NAME
regulatory.bin \- The Linux wireless regulatory database
-.ad l
-.in +8
-.ti -8
-
-.SS
-.SH Description
+.SH DESCRIPTION
.B regulatory.bin
is the file used by the Linux wireless subsystem to keep its regulatory
database information. It is read by
@@ -22,7 +17,7 @@
.B regulatory.bin
file should be updated upon regulatory changes or corrections.
-.SH Upkeeping
+.SH UPKEEP
The regulatory database is maintained by the community as such
you are encouraged to send any corrections or updates to the
linux-wireless mailing list:
next reply other threads:[~2018-06-12 19:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 19:16 esr [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-02-29 11:35 Problems in regulatory.bin.5 esr
2013-06-18 5:13 esr
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=20180612191614.28DC13A4F51@snark.thyrsus.com \
--to=esr@thyrsus.com \
--cc=linux-wireless@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