From: Andy Wingo <wingo@pobox.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: guile-devel@gnu.org, David Pirotte <david@altosw.be>
Subject: Re: guile-lib - devel branch - patch 4 of 11
Date: Sat, 23 Jul 2016 23:01:03 +0200 [thread overview]
Message-ID: <87d1m4rrw0.fsf@pobox.com> (raw)
In-Reply-To: <83vb053s9r.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 17 Jul 2016 05:36:16 +0300")
On Sun 17 Jul 2016 04:36, Eli Zaretskii <eliz@gnu.org> writes:
> If there are known problems with older versions that get in the way, I
> agree. Are there?
>
> If there are no known problems that interfere with maintaining Guile,
> I think refraining from the above will be nicer to our users.
To be clear this is a third-party package called "guile-lib", not Guile
proper.
Regards,
Andy
prev parent reply other threads:[~2016-07-23 21:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-16 1:43 guile-lib - devel branch - patch 4 of 11 David Pirotte
2016-07-16 6:31 ` Eli Zaretskii
2016-07-16 20:34 ` David Pirotte
2016-07-17 2:36 ` Eli Zaretskii
2016-07-17 20:26 ` David Pirotte
2016-07-18 2:40 ` Eli Zaretskii
2016-07-19 23:53 ` David Pirotte
2016-07-20 14:50 ` Eli Zaretskii
2016-07-25 0:05 ` David Pirotte
2016-07-23 21:01 ` 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=87d1m4rrw0.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=david@altosw.be \
--cc=eliz@gnu.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).