From: ludo@gnu.org (Ludovic Courtès)
To: guile-user@gnu.org
Subject: Re: Leap second bug?
Date: Tue, 10 Jun 2008 20:26:43 +0200 [thread overview]
Message-ID: <87hcc15eos.fsf@gnu.org> (raw)
In-Reply-To: 484E9A9D.8020002@wilsonjc.us
Hi,
Jon Wilson <jsw@wilsonjc.us> writes:
> Ludovic Courtès wrote:
>> I'm no expert in that area but I would suggest emailing the SRFI-19
>> mailing list [0] for advice.
>>
>> [0] http://srfi.schemers.org/srfi-19/
>
> This is not recommended, because srfi-19 is "currently unsupported,
> and will likely remain so." [1]
Wow, that sucks given that there is no alternative API (is there?) and
this one is already in widespread use. Some time expert should take it
over.
In the meantime, I guess we just have to make sure we have the same bugs
as others. :-)
Thanks,
Ludovic.
prev parent reply other threads:[~2008-06-10 18:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-07 20:40 Leap second bug? Ondrej Zajicek
2008-06-08 19:45 ` Ondrej Zajicek
2008-06-08 22:00 ` Ludovic Courtès
2008-06-09 14:58 ` Greg Troxel
2008-06-09 17:18 ` Keith Wright
2008-06-10 15:15 ` Jon Wilson
2008-06-10 18:26 ` Ludovic Courtès [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=87hcc15eos.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-user@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).