From: rm@fabula.de
Cc: rm@fabula.de, guile-devel@gnu.org
Subject: Re: Docs missing?
Date: Mon, 5 Aug 2002 21:20:08 +0200 [thread overview]
Message-ID: <20020805192008.GE19325@www> (raw)
In-Reply-To: <m3ado1uokh.fsf@laruns.ossau.uklinux.net>
On Mon, Aug 05, 2002 at 07:51:10PM +0100, Neil Jerram wrote:
> >>>>> "rm" == rm <rm@fabula.de> writes:
>
> rm> Hello list,
> rm> i just realized that the documentation for guardians
> rm> (file: doc/ref/scheme-memory.texi) doesn't mention some
> rm> of the more important scm_* level functions for guardians -
> rm> scm_guard() and scm_get_one_zombie().
> rm> Should i just send a patch? (and if, to whom?).
>
> Assuming that these are intended to be part of the interface, yes
> please. To the list, and I'll apply it sometime later this week.
Probably yes, otherwise scm_make_guardian wouldn't be of much use ;-)
I'll finish the stuff and post it to the list.
Ralf
> Neil
>
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2002-08-05 19:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-05 16:51 Docs missing? rm
2002-08-05 18:51 ` Neil Jerram
2002-08-05 19:20 ` rm [this message]
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020805192008.GE19325@www \
--to=rm@fabula.de \
--cc=guile-devel@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).