From: Lars-Dominik Braun <lars@6xq.net>
To: Saku Laesvuori <saku@laesvuori.fi>
Cc: guix-devel@gnu.org
Subject: Re: Should commits rather be buildable or small
Date: Fri, 8 Dec 2023 13:05:43 +0100 [thread overview]
Message-ID: <ZXMGl9J4l_7qNvLz@noor.fritz.box> (raw)
In-Reply-To: <mcickgfi73ljvgxa7krdtuobuvfo3lvr5d67zqke2f2fbjj4sj@tutctuqoy7ce>
Hi,
> I'm planning on refreshing Guix's haskell packages as my fix for
> https://issues.guix.gnu.org/66347 requires rebuilding all of them
> anyway. Should I try to keep commits small with only one update per
> commit (which is more work but managable if I don't care about the
> commits being buildable) or should I try to keep them buildable (i.e.
> update everything in one commit)?
so far I’ve been updating Haskell packages in bulk in a
single commit. See 49a320aaa6fb4c20d6b30c56c35a8c7ffceed822 or
b97f549b14402421fcfb360ddd4cff7de93b9af0 for example. I also used custom
scripts last time, because `guix refresh` was not sufficient to update
all fields required (arguments, inputs, …). This is hopefully different
this time.
Cheers,
Lars
next prev parent reply other threads:[~2023-12-08 12:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 8:42 Should commits rather be buildable or small Saku Laesvuori
2023-12-08 11:41 ` Tomas Volf
2023-12-08 12:05 ` Lars-Dominik Braun [this message]
2023-12-08 16:35 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-12-08 15:44 ` Liliana Marie Prikler
2023-12-10 15:28 ` Saku Laesvuori
2023-12-10 15:50 ` Liliana Marie Prikler
2023-12-10 17:02 ` Attila Lendvai
2023-12-10 17:50 ` Ricardo Wurmus
2023-12-10 23:20 ` Attila Lendvai
2023-12-10 23:56 ` Philip McGrath
2023-12-11 10:51 ` Attila Lendvai
2023-12-11 11:51 ` Ricardo Wurmus
2024-03-04 21:38 ` John Kehayias
2024-03-05 4:32 ` dan
2024-03-05 5:19 ` Liliana Marie Prikler
2024-03-25 1:15 ` John Kehayias
2024-03-25 3:23 ` dan
2024-03-25 3:23 ` [bug#69461] " dan
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=ZXMGl9J4l_7qNvLz@noor.fritz.box \
--to=lars@6xq.net \
--cc=guix-devel@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 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).