unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: David Kastrup <dak@gnu.org>
Cc: 20109-done@debbugs.gnu.org
Subject: bug#20109: Incompatible API change in 2.0 series for string port encoding
Date: Thu, 23 Jun 2016 19:58:12 +0200	[thread overview]
Message-ID: <87mvmbn5xn.fsf@pobox.com> (raw)
In-Reply-To: <87wplfetum.fsf@fencepost.gnu.org> (David Kastrup's message of "Thu, 23 Jun 2016 18:46:25 +0200")

On Thu 23 Jun 2016 18:46, David Kastrup <dak@gnu.org> writes:

> With regard to Guile 2.0, I cannot provide anything that would warrant
> keeping this report open.

Okeydoke, will close.  Thanks :)

Andy





      reply	other threads:[~2016-06-23 17:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-15 13:15 bug#20109: Incompatible API change in 2.0 series for string port encoding David Kastrup
2015-03-16 20:42 ` Mark H Weaver
2015-03-16 20:46   ` Mark H Weaver
2015-03-17  8:39   ` David Kastrup
2015-03-17 22:44     ` Mark H Weaver
2015-03-18 12:32       ` David Kastrup
2015-04-17  5:17 ` Mark H Weaver
2016-06-23 16:23   ` Andy Wingo
2016-06-23 16:46     ` David Kastrup
2016-06-23 17:58       ` Andy Wingo [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=87mvmbn5xn.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=20109-done@debbugs.gnu.org \
    --cc=dak@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).