From: Heiko Dudzus <heiko.dudzus@gmx.de>
To: Vester Thacker <vester.thacker@gmail.com>,
Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Updating man pages and other documents.
Date: Thu, 9 Dec 2004 11:37:30 +0100 [thread overview]
Message-ID: <20041209103730.GA11609@SDF.LONESTAR.ORG> (raw)
In-Reply-To: <32a656c204120902161fc19bd2@mail.gmail.com>
Vester Thacker wrote:
> I am writing this concerning updating the manual pages and other documents.
> To whom should we send the updates to? And which document format is preferred?
If you made changes to your local system, you can use the patch(1) tools to
put them onto sources.
Document format for man pages is man macros for troff/nroff. It is
decribed in man(6).
next prev parent reply other threads:[~2004-12-09 10:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 10:16 Vester Thacker
2004-12-09 10:28 ` Charles Forsyth
2004-12-09 10:37 ` Heiko Dudzus [this message]
2004-12-09 10:36 ` Charles Forsyth
2004-12-09 11:40 ` Vester Thacker
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=20041209103730.GA11609@SDF.LONESTAR.ORG \
--to=heiko.dudzus@gmx.de \
--cc=9fans@cse.psu.edu \
--cc=vester.thacker@gmail.com \
/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).