From: ludovic.courtes@laas.fr (Ludovic Courtès)
Subject: Re: [PATCH] Fixed `scm_i_take_stringbufn ()'
Date: Tue, 21 Feb 2006 09:37:24 +0100 [thread overview]
Message-ID: <878xs5nm4b.fsf@laas.fr> (raw)
In-Reply-To: <87irrgp9e2.fsf@zip.com.au> (Kevin Ryde's message of "Thu, 16 Feb 2006 09:03:33 +1100")
Hello,
Kevin Ryde <user42@zip.com.au> writes:
> No, in 1.8. Someone can do merges into the head (there isn't anything
> in 1.8 which isn't also meant to be in the head, yet).
Did "someone" do that merge? :-)
I'm afraid we're going to forget some stuff in one or another branch...
Thanks,
Ludovic.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-02-21 8:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 16:38 [PATCH] Fixed `scm_i_take_stringbufn ()' Ludovic Courtès
2006-02-13 21:38 ` Kevin Ryde
2006-02-14 9:47 ` Ludovic Courtès
2006-02-15 0:38 ` Kevin Ryde
2006-02-15 7:58 ` Ludovic Courtès
2006-02-15 22:03 ` Kevin Ryde
2006-02-21 8:37 ` Ludovic Courtès [this message]
2006-02-15 0:48 ` Kevin Ryde
2006-02-15 8:01 ` Ludovic Courtès
2006-02-15 22:15 ` 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=878xs5nm4b.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).