From: Lars-Dominik Braun <lars@6xq.net>
To: Saku Laesvuori <saku@laesvuori.fi>
Cc: 67564-done@debbugs.gnu.org
Subject: bug#67564: [PATCH 0/3] Fixes for haskell importers
Date: Sun, 3 Dec 2023 09:13:46 +0100 [thread overview]
Message-ID: <ZWw4ugrDqSk9eU0v@noor.fritz.box> (raw)
In-Reply-To: <x54ow4nedj36izmr7aqzivzpm42nkj46sz3yyy2celravzfkwu@4jahbsnbarin>
Hi,
> Done in v2. There was already a test for this that was expected to fail.
> I just marked it to be expected to pass instead.
yes, you’re right. Merged as:
5bd00bb54235856dddd11e9f0d03481c5469ca63 guix: import: Parse cabal layout blocks correctly
acef524961d4da3464dbc392699fbe7deb0a467b guix: import: stackage: Fix crash on recursive import
160385c013b0403af427b61b1d1cc9a75bc3315d guix: import: hackage: Fix crash on recursive import
Thanks you very much!
Lars
next prev parent reply other threads:[~2023-12-03 8:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 9:24 [bug#67564] [PATCH 0/3] Fixes for haskell importers Saku Laesvuori via Guix-patches via
2023-12-01 9:29 ` [bug#67564] [PATCH 1/3] guix: import: hackage: Fix crash on recursive import Saku Laesvuori via Guix-patches via
2023-12-01 9:29 ` [bug#67564] [PATCH 2/3] guix: import: stackage: " Saku Laesvuori via Guix-patches via
2023-12-01 9:29 ` [bug#67564] [PATCH 3/3] guix: import: Parse cabal layout blocks correctly Saku Laesvuori via Guix-patches via
2023-12-01 15:06 ` [bug#67564] [PATCH 0/3] Fixes for haskell importers Lars-Dominik Braun
2023-12-02 17:27 ` Saku Laesvuori via Guix-patches via
2023-12-03 8:13 ` Lars-Dominik Braun [this message]
2023-12-02 17:23 ` [bug#67564] [PATCH v2 1/3] guix: import: hackage: Fix crash on recursive import Saku Laesvuori via Guix-patches via
2023-12-02 17:23 ` [bug#67564] [PATCH v2 2/3] guix: import: stackage: " Saku Laesvuori via Guix-patches via
2023-12-02 17:23 ` [bug#67564] [PATCH v2 3/3] guix: import: Parse cabal layout blocks correctly Saku Laesvuori via Guix-patches via
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZWw4ugrDqSk9eU0v@noor.fritz.box \
--to=lars@6xq.net \
--cc=67564-done@debbugs.gnu.org \
--cc=saku@laesvuori.fi \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.