From: Kevin Ryde <user42@zip.com.au>
Subject: Re: srfi-1 delete proc arg order
Date: Sat, 17 May 2003 09:37:31 +1000 [thread overview]
Message-ID: <87r86yo43o.fsf@zip.com.au> (raw)
In-Reply-To: <87addn8w55.fsf@raven.i.defaultvalue.org> (Rob Browning's message of "Thu, 15 May 2003 21:26:14 -0500")
Rob Browning <rlb@defaultvalue.org> writes:
>
> Actually, not. Any changes need to be applied to both trees since
> they're completely separate, and may have differing sets of changes.
I might be nice for users if the news looked like a single sequence,
even if it's not developed that way. But anyway, I added to the head.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-05-16 23:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 3:59 srfi-1 delete proc arg order Kevin Ryde
2003-05-12 23:03 ` Kevin Ryde
2003-05-12 23:49 ` Rob Browning
2003-05-13 17:44 ` Marius Vollmer
2003-05-16 1:06 ` Kevin Ryde
2003-05-16 2:26 ` Rob Browning
2003-05-16 23:37 ` Kevin Ryde [this message]
2003-05-17 0:06 ` Rob Browning
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=87r86yo43o.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).