From: "Richard Hartmann" <richih.mailinglist@gmail.com>
To: "Zsh Workers" <zsh-workers@sunsite.dk>
Subject: Suggestion for a new doc style
Date: Sun, 28 Dec 2008 12:52:48 +0100 [thread overview]
Message-ID: <2d460de70812280352l53c56b27qea97dbb4659c709b@mail.gmail.com> (raw)
Hi all,
I just found out about the new(?) compsys rehash and wondered
when it was introduced so I could replace/amend my own
rehash blurb in my .zshrc.
Thus, I wanted to suggest that all _new_ docs that ware written
have a term like '(introduced in x.y.z)' appended to them.
It would not be much work and build up, over time. If this is
done, I will probably go through the entries lacking that info on
an idle weekend so the old entries get up on par.
Richard
next reply other threads:[~2008-12-28 11:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-28 11:52 Richard Hartmann [this message]
2008-12-29 1:46 ` Bart Schaefer
2008-12-29 2:14 ` Richard Hartmann
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=2d460de70812280352l53c56b27qea97dbb4659c709b@mail.gmail.com \
--to=richih.mailinglist@gmail.com \
--cc=zsh-workers@sunsite.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).