From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: socket.c
Date: Sun, 01 Feb 2004 15:34:05 -0600 [thread overview]
Message-ID: <87oesilc1e.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <5B00101A-54F4-11D8-969F-000A95C37894@lurchi.franken.de> (Michael Tuexen's message of "Sun, 1 Feb 2004 21:22:28 +0100")
Michael Tuexen <Michael.Tuexen@lurchi.franken.de> writes:
> I would like to extend socket.c such that guile supports also SCTP.
> If I submit patches against the 1.6.4 version is it possible that
> the changes are included in the 1.6.5 release? Or should I submit
> patches against the CVS version? Is it still possible to include the
> changes into 1.6.5?
It would depend on the nature of the changes. For example, I'm about
to add srfi-31 to 1.6 and 1.7, but that will only involve the addition
of a new file, a new test, and some documentation, and nothing should
be affected unless you (use-modules (srfi srfi-31)).
It would defintely be a judgement call. If the changes can be done in
such a way that it's obvious that they won't break existing build or
runtime behaviors, then that'd be fine, but it's worth mentioning that
we're very likely to err on the side of being conservative with
changes to 1.6.
Hope this helps.
--
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 21:34 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 ` Rob Browning [this message]
2004-02-01 21:59 ` socket.c Michael Tuexen
2004-02-01 22:19 ` socket.c Rob Browning
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=87oesilc1e.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).