From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Re: cont-doc module
Date: Wed, 17 Dec 2003 22:08:44 +0100 [thread overview]
Message-ID: <6.0.1.1.2.20031217220816.02e15af0@server-1> (raw)
In-Reply-To: <005e01c3c3ec$14caa970$01fd5644@playroom>
At 16:48 16/12/2003, you wrote:
>Ditto here, regardless of what file I try to process.
>Question: Generally do source files contain documentation that goes beyond
>(or is more up to date) than the manual?
no, but i sometimes mix up interfaces (seldom run documentation -)
so just let me know where thinsg go wrong and i'll fix 'm
Hans
next prev parent reply other threads:[~2003-12-17 21:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5.1.0.14.1.20021009162947.02178ad0@server-1>
2003-12-15 17:15 ` Hans van der Meer
2003-12-16 15:48 ` Gary Pajer
2003-12-17 21:08 ` Hans Hagen [this message]
2003-12-17 21:04 ` Hans Hagen
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=6.0.1.1.2.20031217220816.02e15af0@server-1 \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
/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).