From: Lars-Dominik Braun <lars@6xq.net>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: Merging branch wip-haskell
Date: Wed, 15 Feb 2023 10:45:47 +0100 [thread overview]
Message-ID: <Y+ypyzP1B4MNglAS@noor.fritz.box> (raw)
In-Reply-To: <Y+ymhsf4xuxYJTDW@jurong>
Hi Andreas,
> I do not think we should coordinate, this was part of the motivation for
> considering feature branches in the first place, to avoid entanglement
> with different updates.
ah, alright. I’ll give everyone more time for reviews and then just
merge it.
> However, QA has not run yet:
> https://qa.guix.gnu.org/issue/61420
> I assume it will start in a few days, so maybe you could wait a little bit
> until it has run and hopefully provided substitutes on bordeaux?
There’s a job on CI already: https://ci.guix.gnu.org/jobset/wip-haskell
> By the way, there are also branches wip-haskell-updates and
> wip-haskell-updates-2 from 2020; maybe they can be deleted?
Yeah, I guess we can remove them.
Cheers,
Lars
next prev parent reply other threads:[~2023-02-15 9:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 9:01 Merging branch wip-haskell Lars-Dominik Braun
2023-02-15 9:31 ` Andreas Enge
2023-02-15 9:45 ` Lars-Dominik Braun [this message]
2023-02-15 9:48 ` Andreas Enge
2023-02-15 10:38 ` zimoun
2023-02-22 9:37 ` Andreas Enge
2023-02-22 10:54 ` Efraim Flashner
2023-03-07 20:24 ` Andreas Enge
2023-02-26 9:47 ` Lars-Dominik Braun
2023-02-27 10:47 ` Simon Tournier
2023-02-27 11:04 ` Lars-Dominik Braun
2023-02-27 11:55 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-03-08 17:51 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-03-08 19:31 ` Lars-Dominik Braun
2023-03-08 19:43 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-03-09 2:15 ` Cuirass package build timeouts and max-silent-time [was Re: Merging branch wip-haskell] Leo Famulari
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=Y+ypyzP1B4MNglAS@noor.fritz.box \
--to=lars@6xq.net \
--cc=andreas@enge.fr \
--cc=guix-devel@gnu.org \
/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).