From: ludovic.courtes@laas.fr (Ludovic Courtès)
Subject: [PATCH] Docstring for `setsockopt'
Date: Mon, 07 Nov 2005 17:16:41 +0100 [thread overview]
Message-ID: <874q6oh1qu.fsf@laas.fr> (raw)
Hi,
A small fix to the docstring of `setsockopt'.
Thanks,
Ludovic.
2005-11-07 Ludovic Courtès <ludovic.courtes@laas.fr>
* socket.c (scm_setsockopt): Appended `@end defvar' to the
docstring.
--- orig/libguile/socket.c
+++ mod/libguile/socket.c
@@ -626,7 +626,8 @@
"dropped from the interface @var{INTERFACEADDR}.\n"
"@var{INTERFACEADDR} can be @code{INADDR_ANY} to have the system\n"
"select the interface. @var{INTERFACEADDR} can also be an\n"
- "interface index number, on systems supporting that.")
+ "interface index number, on systems supporting that.\n"
+ "@end defvar\n")
#define FUNC_NAME s_scm_setsockopt
{
int fd;
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2005-11-07 16:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-07 16:16 Ludovic Courtès [this message]
2005-11-12 0:58 ` [PATCH] Docstring for `setsockopt' Kevin Ryde
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=874q6oh1qu.fsf@laas.fr \
--to=ludovic.courtes@laas.fr \
/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).