From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: HEADSUP: gdbm ABI on x86
Date: Sat, 15 Oct 2016 17:36:00 -0000 [thread overview]
Message-ID: <7d146023-41d2-a1ca-f0fe-a432f1128242@cornell.edu> (raw)
In-Reply-To: <878ttpsf2n.fsf@Rainer.invalid>
On 10/15/2016 1:21 PM, Achim Gratz wrote:
> Ken Brown writes:
>> I've rebuilt this (x86 only) and uploaded it to my release area. I
>> won't upload the !ready file until Achim has a chance to rebuild
>> maxima.
>
> I'm standing by with the maxima rebuild (actually I've done a minor update
> to 5.38.1).
OK, I'll go ahead with the !ready file in about 10 minutes.
Ken
next prev parent reply other threads:[~2016-10-15 17:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 19:55 Yaakov Selkowitz
2016-10-11 15:50 ` HEADSUP: gdbm ABI on x86 (DONE qsf suck - rebuilt and uploaded) Jari Aalto
2016-10-11 19:17 ` HEADSUP: gdbm ABI on x86 Ken Brown
2016-10-11 19:26 ` Achim Gratz
2016-10-15 17:22 ` Achim Gratz
2016-10-15 17:36 ` Ken Brown [this message]
2016-10-15 17:37 ` Achim Gratz
2016-10-15 17:40 ` Ken Brown
2016-10-15 17:43 ` Achim Gratz
2016-10-11 19:24 ` Achim Gratz
2017-02-22 19:57 ` Yaakov Selkowitz
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7d146023-41d2-a1ca-f0fe-a432f1128242@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-apps@cygwin.com \
/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).