From: "Stone, Joshua I" <joshua.i.stone@intel.com>
To: Mike Mason <mmlnx@us.ibm.com>
Cc: SystemTAP <systemtap@sources.redhat.com>
Subject: Re: Online documentation and version differences
Date: Fri, 09 Nov 2007 18:19:00 -0000 [thread overview]
Message-ID: <20071109181846.GA22956@jistone-expr.sc.intel.com> (raw)
In-Reply-To: <4734905E.8070204@us.ibm.com>
Mike Mason wrote:
> One week ago I posted this concern regarding the accuracy of the language
> reference and have received no responses so far. Did it not make it to the
> list? I'd like others opinions on how to keep the language reference
> accurate for multiple versions.
It does sound reasonable to package the reference into the RPM, just as
we do for the man pages. Something like /usr/share/systemtap/doc/ would
be fine.
For online docs, we could keep an archive for released versions as many
other projects do. We may need to get more formal about what a released
version means though...
Josh
next prev parent reply other threads:[~2007-11-09 18:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-02 16:12 Mike Mason
2007-11-09 16:53 ` Mike Mason
2007-11-09 18:19 ` Stone, Joshua I [this message]
2007-11-09 18:46 ` Frank Ch. Eigler
2008-02-28 2:37 ` Frank Ch. Eigler
2008-03-03 15:40 ` Masami Hiramatsu
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=20071109181846.GA22956@jistone-expr.sc.intel.com \
--to=joshua.i.stone@intel.com \
--cc=mmlnx@us.ibm.com \
--cc=systemtap@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).