unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Vollmert <rob@vllmrt.net>
To: Timothy Sample <samplet@ngyro.com>
Cc: guix-devel@gnu.org, 36807@debbugs.gnu.org
Subject: Re: Please merge wip-haskell-updates (Re: [bug#36807] remove obsolete broken haskell packages)
Date: Tue, 6 Aug 2019 09:49:32 +0200	[thread overview]
Message-ID: <CE996BBE-0059-4485-8733-09CF5A6381FC@vllmrt.net> (raw)
In-Reply-To: <87mugmq5ll.fsf@ngyro.com>

Oh, I meant to ask:

On 6. Aug 2019, at 06:29, Timothy Sample <samplet@ngyro.com> wrote:
> Robert Vollmert <rob@vllmrt.net> writes:
> 
>> Hi all, Timothy,
> 
> Cool!  I’m in the process of looking everything over.  In the meantime,
> I have some early questions and comments.
> 
>> I’ve incorporated your comments, and removed
>> ghc-packedstring. In addition, the branch incorporates some other
>> patchsets:
>> 
>> #36493: updating GHC-included haskell dependencies (this one is already
>>        in core-updates)
> 
> I think it makes sense to wait for the core-updates merge (which
> shouldn’t be too far out).

Why? Shouldn’t substitutes be available since CI built the branch successfully?

  parent reply	other threads:[~2019-08-06  7:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <F5E8BA95-BE79-4579-B881-AE0862B69D3A@vllmrt.net>
     [not found] ` <87muh2ckdn.fsf@ngyro.com>
2019-08-01 16:23   ` Please merge wip-haskell-updates (Re: [bug#36807] remove obsolete broken haskell packages) Robert Vollmert
2019-08-06  4:29     ` Timothy Sample
2019-08-06  7:04       ` Robert Vollmert
2019-08-08  3:42         ` Timothy Sample
2019-08-06  7:49       ` Robert Vollmert [this message]
2019-08-07 11:19         ` Marius Bakke
2019-08-08  3:47           ` Timothy Sample
2019-08-08 13:12             ` Marius Bakke
2019-08-08 13:42               ` Robert Vollmert
2019-08-08 15:54                 ` Timothy Sample
2019-08-08 16:08                   ` Marius Bakke

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=CE996BBE-0059-4485-8733-09CF5A6381FC@vllmrt.net \
    --to=rob@vllmrt.net \
    --cc=36807@debbugs.gnu.org \
    --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).