From: John Soo <jsoo1@asu.edu>
To: Robert Vollmert <rob@vllmrt.net>
Cc: 36545@debbugs.gnu.org
Subject: [bug#36545] [PATCH] Add Hoogle
Date: Fri, 16 Aug 2019 13:58:33 +0000 [thread overview]
Message-ID: <CAKf5CqXGCZu1czwHkhRT5QgKspy-hP4jooWWAEsHppEr+qnuDw@mail.gmail.com> (raw)
In-Reply-To: <24FFD6A0-24D2-4145-B829-20B43C0C5BA6@vllmrt.net>
[-- Attachment #1: Type: text/plain, Size: 1018 bytes --]
Excellent, thank you!
On Fri, Aug 16, 2019 at 12:22 PM Robert Vollmert <rob@vllmrt.net> wrote:
> Hi John,
>
> looks good to me! Hoogle builds and fine, and seems to run.
>
> I’ve applied the patches to the wip-haskell-updates branch, will see
> to get that merged soon.
>
> Cheers
> Robert
>
> > On 16. Aug 2019, at 07:58, John Soo <jsoo1@asu.edu> wrote:
> >
> > Hi Robert and Guix,
> >
> > I realized just now that I had some incorrect git configuration. I have
> attached the updated patches with my correct email address.
> >
> > Thanks again!
> >
> > - John
> >
> <0004-gnu-Add-ghc-storablevector.patch><0005-gnu-Add-ghc-fmlist.patch><0002-gnu-Add-ghc-non-negative.patch><0001-gnu-Add-ghc-unsafe.patch><0003-gnu-Add-ghc-timeit.patch><0007-gnu-Add-ghc-listlike.patch><0006-gnu-Add-ghc-storable-record.patch><0008-gnu-Add-ghc-storable-tuple.patch><0009-gnu-Add-ghc-process-extras.patch><0010-gnu-Add-ghc-js-jquery.patch><0011-gnu-Add-ghc-js-flot.patch><0012-gnu-Add-hoogle.patch>
>
>
[-- Attachment #2: Type: text/html, Size: 1493 bytes --]
next prev parent reply other threads:[~2019-08-16 13:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 6:10 [bug#36545] [PATCH] Add Hoogle John Soo
2019-07-09 17:37 ` [bug#36545] two issues Robert Vollmert
2019-08-15 17:09 ` [bug#36545] [PATCH] Add Hoogle John Soo
[not found] ` <CAKf5CqUnmr0fuEC6WCnEH1eK30tp4pDsWKW05K0MGq8fL8ZRPg@mail.gmail.com>
2019-08-16 5:58 ` John Soo
2019-08-16 12:22 ` Robert Vollmert
2019-08-16 13:58 ` John Soo [this message]
2019-09-03 3:18 ` bug#36545: " Timothy Sample
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=CAKf5CqXGCZu1czwHkhRT5QgKspy-hP4jooWWAEsHppEr+qnuDw@mail.gmail.com \
--to=jsoo1@asu.edu \
--cc=36545@debbugs.gnu.org \
--cc=rob@vllmrt.net \
/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).