From: Ricardo Wurmus <rekado@elephly.net>
To: Timothy Sample <samplet@ngyro.com>
Cc: guix-devel@gnu.org
Subject: Re: merge wip-haskell?
Date: Sat, 15 Aug 2020 10:19:41 +0200 [thread overview]
Message-ID: <87v9hkqq1u.fsf@elephly.net> (raw)
In-Reply-To: <87k0y236ce.fsf@elephly.net>
Ricardo Wurmus <rekado@elephly.net> writes:
> Timothy Sample <samplet@ngyro.com> writes:
>
>> I just pushed “wip-haskell-updates-2” which integrates my work from
>> <https://issues.guix.gnu.org/39309>. I left the original branch intact
>> to make it easy to compare.
>
> I rebased this on top of “master” and pushed it as “wip-haskell”. I
> updated my changes to pandoc and pandoc-citeproc so that the statically
> linked variants are now separate packages.
>
> The evaluations on ci.guix.gnu.org failed due to a few minor bugs in the
> extra-directories code (missing “match” case for inputs with declared
> outputs, and a missing list wrapper in one package). I fixed up that
> commit and now wait for ci.guix.gnu.org to start building things:
>
> https://ci.guix.gnu.org/jobset/wip-haskell
I just merged “wip-haskell” into “master” (after merging “master” into
“wip-haskell”).
--
Ricardo
next prev parent reply other threads:[~2020-08-15 16:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 8:13 merge wip-haskell? Ricardo Wurmus
2020-08-06 13:45 ` John Soo
2020-08-07 17:46 ` Timothy Sample
2020-08-07 19:53 ` Ricardo Wurmus
2020-08-09 4:29 ` Timothy Sample
2020-08-12 12:21 ` Ricardo Wurmus
2020-08-13 15:37 ` Ricardo Wurmus
2020-08-15 8:19 ` Ricardo Wurmus [this message]
2020-08-17 15:22 ` Timothy Sample
2020-08-24 15:38 ` Ludovic Courtès
2020-08-07 15:03 ` Jakub Kądziołka
2020-08-07 15:12 ` John Soo
2020-08-07 15:46 ` Jakub Kądziołka
2020-08-07 15:59 ` Ricardo Wurmus
2020-08-07 16:08 ` John Soo
2020-08-24 15:44 ` Ludovic Courtès
2020-08-24 17:54 ` Ricardo Wurmus
2020-08-28 13:53 ` Ludovic Courtès
2020-08-28 14:05 ` John Soo
2020-08-28 17:29 ` Timothy Sample
2020-08-29 15:34 ` Timothy Sample
2020-08-29 15:54 ` John Soo
2020-08-07 16:27 ` Ricardo Wurmus
2020-08-07 16:55 ` Jakub Kądziołka
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=87v9hkqq1u.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=samplet@ngyro.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.
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).