From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: coreutils@gnu.org, linux-man@vger.kernel.org
Subject: Re: Move GNU manual pages to the Linux man-pages project
Date: Tue, 30 Sep 2025 08:35:48 -0500 [thread overview]
Message-ID: <20250930133548.6e33lxc6ptync2hd@illithid> (raw)
In-Reply-To: <e369c200-a7cd-4b92-b700-d9d48d347ce8@landley.net>
[-- Attachment #1: Type: text/plain, Size: 784 bytes --]
At 2025-09-30T08:23:10-0500, Rob Landley wrote:
> Either people updated the docs or they didn't. Having an active
> well-known place to go look and complain at is useful. Requiring
> somebody to read the source code and provide a copyright assignment to
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> tweak documentation... well you've tried that since 1983, how did it
> go?
Wrong since (at least) 2013 and wrong today.
https://lists.gnu.org/archive/html/gnustandards-commit/2013-10/msg00000.html
> There may be some selection bias in the people who constantly read and
> edit this source code finding this source code to be the best place to
> put the docs. Learn to cook at the oven factory.
Or play ill-informed games in a toy box.
Regards,
Branden
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-09-30 13:35 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-20 16:08 Move GNU manual pages to the Linux man-pages project Alejandro Colomar
2025-09-20 16:27 ` Sam James
2025-09-20 16:50 ` Alejandro Colomar
2025-09-20 17:00 ` Alejandro Colomar
2025-09-20 16:34 ` Pádraig Brady
2025-09-20 16:55 ` Alejandro Colomar
2025-09-20 17:01 ` Pádraig Brady
2025-09-20 17:04 ` Alejandro Colomar
2025-09-20 20:05 ` Collin Funk
2025-09-20 21:05 ` Alejandro Colomar
2025-09-20 23:02 ` Collin Funk
2025-09-21 8:36 ` Alejandro Colomar
[not found] ` <PA3P190MB24382227EA61EC2758D5AA11C410A@PA3P190MB2438.EURP190.PROD.OUTLOOK.COM>
2025-09-20 23:18 ` Collin Funk
2025-09-22 15:06 ` Michael Greenberg
2025-09-20 17:42 ` Jakub Wilk
2025-09-20 21:10 ` Alejandro Colomar
2025-09-20 21:22 ` Collin Funk
2025-09-21 8:28 ` Bernhard Voelker
2025-09-21 20:00 ` Chuck Wolber
2025-09-21 12:02 ` Arsen Arsenović
2025-09-21 12:53 ` Alejandro Colomar
2025-09-25 14:04 ` Arsen Arsenović
2025-09-25 14:31 ` Alejandro Colomar
2025-09-29 9:46 ` Arsen Arsenović
2025-09-29 10:33 ` Alejandro Colomar
2025-09-29 21:26 ` Arsen Arsenović
2025-09-29 21:38 ` Alejandro Colomar
2025-09-29 21:41 ` Pádraig Brady
2025-09-29 23:27 ` Alejandro Colomar
2025-09-30 10:12 ` Pádraig Brady
2025-09-30 21:14 ` Bernhard Voelker
2025-09-30 13:23 ` Rob Landley
2025-09-30 13:35 ` G. Branden Robinson [this message]
2025-09-30 19:57 ` Arsen Arsenović
2025-09-30 20:55 ` G. Branden Robinson
2025-10-01 13:21 ` Arsen Arsenović
2025-10-01 19:37 ` Rob Landley
2025-10-02 18:46 ` Arsen Arsenović
2025-10-02 20:48 ` G. Branden Robinson
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=20250930133548.6e33lxc6ptync2hd@illithid \
--to=g.branden.robinson@gmail.com \
--cc=coreutils@gnu.org \
--cc=linux-man@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