From: Federico Beffa <beffa@ieee.org>
To: rekado@elephly.net
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH 2/2] gnu: ghc-process: Replace reference to /bin/sh.
Date: Sun, 2 Oct 2016 17:51:30 +0200 [thread overview]
Message-ID: <CAKrPhPPGOQnUR_PgKAnHLXnFwcKfj9TuxD5Qfi2jkO5oEi4pcQ@mail.gmail.com> (raw)
Ricardo Wurmus <rekado@elephly.net> writes:
> The importer should probably avoid adding standard packages to the
> inputs.
The importer does filter standard packages. The list may just have to
be updated.
next reply other threads:[~2016-10-02 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-02 15:51 Federico Beffa [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-10-01 15:51 [PATCH 1/2] gnu: Do not propagate inputs in haskell.scm Ricardo Wurmus
2016-10-01 15:51 ` [PATCH 2/2] gnu: ghc-process: Replace reference to /bin/sh Ricardo Wurmus
2016-10-02 13:41 ` Ludovic Courtès
2016-10-02 15:03 ` Ricardo Wurmus
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=CAKrPhPPGOQnUR_PgKAnHLXnFwcKfj9TuxD5Qfi2jkO5oEi4pcQ@mail.gmail.com \
--to=beffa@ieee.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.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).