From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: socket.c
Date: Sun, 01 Feb 2004 16:19:42 -0600 [thread overview]
Message-ID: <873c9ul9xd.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <E0E5C645-5501-11D8-A010-000A95C37894@lurchi.franken.de> (Michael Tuexen's message of "Sun, 1 Feb 2004 22:59:16 +0100")
Michael Tuexen <Michael.Tuexen@lurchi.franken.de> writes:
> So should I code against the 1.6.4 socket.c file or the
> one in the CVS? Do I have better chances to get the stuff
> into 1.6.5 when coding against the 1.6.4 version?
Definitely code against the 1.6 branch. From CVS, update or checkout
with "-r branch_release-1-6", though if you're concerned about
acceptance, you might want to wait a day or so to see if there are any
other strong objections.
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-02-01 22:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-01 20:22 socket.c Michael Tuexen
2004-02-01 21:34 ` socket.c Rob Browning
2004-02-01 21:59 ` socket.c Michael Tuexen
2004-02-01 22:19 ` Rob Browning [this message]
2004-02-01 22:40 ` socket.c Michael Tuexen
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=873c9ul9xd.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--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).