From: Andreas Enge <andreas@enge.fr>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: guix-devel@gnu.org, bavier@member.fsf.org
Subject: Re: Anyone using libhilbert?
Date: Tue, 29 Aug 2017 22:32:47 +0200 [thread overview]
Message-ID: <20170829203247.GB2272@jurong> (raw)
In-Reply-To: <db1b8574-31fd-ff33-ebfb-cf1c0582f853@tobias.gr>
On Tue, Aug 29, 2017 at 09:13:03PM +0200, Tobias Geerinckx-Rice wrote:
> It's not the easiest package or author to track down, and I lost
> interest after a while since I'm not really familiar with either.
I think this is the author's new web page:
https://www.lpl.arizona.edu/hamilton/
I just tracked it down for the fun of it, and am not interested in
the package myself.
Andreas
next prev parent reply other threads:[~2017-08-29 20:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 19:13 Anyone using libhilbert? Tobias Geerinckx-Rice
2017-08-29 20:32 ` Andreas Enge [this message]
2017-08-29 20:35 ` Andreas Enge
2017-09-08 19:09 ` Eric Bavier
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170829203247.GB2272@jurong \
--to=andreas@enge.fr \
--cc=bavier@member.fsf.org \
--cc=guix-devel@gnu.org \
--cc=me@tobias.gr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).