9front - general discussion about 9front
 help / color / mirror / Atom feed
From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] 9front man pages
Date: Fri, 8 Mar 2024 12:34:25 +0100	[thread overview]
Message-ID: <CAFSF3XM2934cT55ajn4mrHTFeuzg-rrkrg6hnSOzThS86PwQbg@mail.gmail.com> (raw)
In-Reply-To: <CAFSF3XPqjPwBxVBUwUKOAiJ_dJ5vhEVRffdJruC6jcFkDMqPdA@mail.gmail.com>

Also, generally, I think *not* having a disparate "documentation team"
is a feature, so far.
I prefer it when people change code (and relevant documentation)
gradually. If you add a new feature, this will require obvious
additions to the documentation. If this entitles you to touch the
documentation anyways, I understand you might rework the surrounding
sentences slightly to make more sense. But redoing everything from the
ground up is not something we generally do here just for the sake of
keeping busy.
If the documentation has a bug, send a patch. People regularly make
errors, forget things, etc. But keep the changes minimal.

  reply	other threads:[~2024-03-08 11:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-08  4:47 eso
2024-03-08  5:07 ` Jacob Moody
2024-03-08  5:28   ` Roberto E. Vargas Caballero
2024-03-08  9:01     ` qwx
2024-03-08 11:30       ` hiro
2024-03-08 11:34         ` hiro [this message]
2024-03-08 11:35           ` hiro
2024-03-08 16:01           ` eso
2024-03-08 16:24             ` qwx
2024-03-08  5:23 ` ori
2024-03-08 17:40   ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2024-03-08 18:30     ` hiro
2024-03-08 23:20       ` umbraticus
2024-03-08 23:50         ` ori
2024-03-09  0:40           ` sl
2024-03-09  1:08             ` hiro
2024-03-09  1:36               ` Stanley Lieber
2024-03-09 11:01                 ` sirjofri
2024-03-10 19:16                   ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2024-03-10 21:05                     ` sirjofri
2024-03-10 21:11                     ` hiro

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=CAFSF3XM2934cT55ajn4mrHTFeuzg-rrkrg6hnSOzThS86PwQbg@mail.gmail.com \
    --to=23hiro@gmail.com \
    --cc=9front@9front.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).