From: Marius Bakke <mbakke@fastmail.com>
To: Ricardo Wurmus <rekado@elephly.net>, Timothy Sample <samplet@ngyro.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Stackage LTS 14 (was: Adding Purescript)
Date: Wed, 23 Oct 2019 19:59:40 +0200 [thread overview]
Message-ID: <87ftjjwdf7.fsf@devup.no> (raw)
In-Reply-To: <87a79tj8mq.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 1361 bytes --]
Ricardo Wurmus <rekado@elephly.net> writes:
> Hi Timothy,
>
>> One of the things I want to do this time is to do the upgrade in one
>> mega commit. I’m pretty sure that some of the commits last time had
>> inconsistent package sets, which is not ideal. I’m not sure how to
>> avoid that upgrading one package at a time. Hence, my rough plan is to
>> start by setting GHC 8.6 as the compiler for the build system, and then
>> run the refresh script with Stackage LTS 14. After that, I will push
>> the results to wip-haskell-updates and see how it goes.
>>
>> Ricardo, what do you think? Are we okay to take over
>> wip-haskell-updates? Does a mega commit make sense or do you think
>> that’s a bad idea?
>
> Yes, you can take over wip-haskell-updates.
>
> A single big commit is not a good idea, but you don’t really need it as
> you’d merge the branch in one go, so Cuirass would not end up evaluating
> any of the intermediate commits anyway. It’s still good to have smaller
> commits to better undo individual changes and more easily understand
> related changes.
AIUI individual updates cannot really be un-done, because that would
break the entire dependency chain.
I think it's OK to "squash" instances like this, both to clarify that
the changes are in fact related, and to make bisecting less painful.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-10-23 17:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 20:42 Adding Purescript John Soo
2019-10-22 0:32 ` Stackage LTS 14 (was: Adding Purescript) Timothy Sample
2019-10-22 11:57 ` Ricardo Wurmus
2019-10-23 17:59 ` Marius Bakke [this message]
2019-11-01 4:07 ` Stackage LTS 14 Timothy Sample
2019-11-04 5:16 ` Timothy Sample
2019-11-09 5:12 ` Timothy Sample
2019-11-12 6:58 ` Timothy Sample
2019-11-12 16:16 ` John Soo
2019-11-12 20:18 ` Timothy Sample
2019-11-14 9:38 ` John Soo
2019-11-14 14:53 ` Timothy Sample
2019-11-14 15:18 ` Marius Bakke
2019-11-14 19:03 ` John Soo
2019-11-14 20:30 ` Timothy Sample
2019-11-14 21:09 ` John Soo
2019-11-17 0:42 ` Timothy Sample
2019-11-17 16:13 ` Timothy Sample
2019-11-19 22:16 ` Marius Bakke
2019-11-21 2:20 ` Timothy Sample
2019-11-21 4:40 ` John Soo
2019-11-21 10:12 ` Efraim Flashner
2019-11-21 18:32 ` 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=87ftjjwdf7.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
--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).