From: ludovic.courtes@laas.fr (Ludovic Courtès)
Cc: bug-guile@gnu.org, Neil Jerram <neil@ossau.uklinux.net>
Subject: Re: libguile/socket.c
Date: Fri, 10 Feb 2006 09:37:09 +0100 [thread overview]
Message-ID: <87oe1ffw3u.fsf@laas.fr> (raw)
In-Reply-To: <87hd782ojx.fsf@zagadka.de> (Marius Vollmer's message of "Thu, 09 Feb 2006 23:46:26 +0200")
Hi,
Marius Vollmer <mvo@zagadka.de> writes:
> Please also make this change in the branch_release-1-8 branch if
> appropriate.
BTW, what's going to be put in HEAD from now on (apart from what goes in
the 1.8 branch)?
Thanks,
Ludovic.
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
prev parent reply other threads:[~2006-02-10 8:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 8:43 libguile/socket.c hyperdivision
2006-02-09 10:10 ` libguile/socket.c Neil Jerram
2006-02-09 12:01 ` libguile/socket.c Ludovic Courtès
2006-02-09 13:43 ` libguile/socket.c Neil Jerram
2006-02-09 21:46 ` libguile/socket.c Marius Vollmer
2006-02-10 6:58 ` libguile/socket.c Neil Jerram
2006-02-10 8:21 ` libguile/socket.c Marius Vollmer
2006-02-10 8:37 ` Ludovic Courtès [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=87oe1ffw3u.fsf@laas.fr \
--to=ludovic.courtes@laas.fr \
--cc=bug-guile@gnu.org \
--cc=neil@ossau.uklinux.net \
/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).