From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Greg Hogan <code@greghogan.com>, 60042@debbugs.gnu.org
Subject: [bug#60042] [PATCH] gnu: git: Update to 2.39.0.
Date: Tue, 20 Dec 2022 16:38:46 +0100 [thread overview]
Message-ID: <CAJ3okZ3j+HTATsoGE978b+LGk0KAEM7-BAGSy_Gtm61FzTWwQA@mail.gmail.com> (raw)
In-Reply-To: <87edsu6sbp.fsf_-_@gnu.org>
Hi Ludo,
On Tue, 20 Dec 2022 at 15:52, Ludovic Courtès <ludo@gnu.org> wrote:
> According to figures in the manual, it’s for ‘staging’ (info "(guix)
> Submitting Patches"). But I guess those figures are less appropriate
> now that the package collection and build farms have grown. We’ll have
> to think about it!
On one hand, I agree that these numbers could be revisited on the
light of the new QA. On the other hand, this "trivial" patch implies
a Julia (almost) world rebuild -- so potentially some breakages. And
personally, I cannot run again and again after broken packages from
unrelated changes. :-)
Well, if the new QA is able to deal with heavy rebuilds, yeah for
sure, if all is green and the patch does not introduce any breakage,
there is no reason for not merging. However, if you go to the
dashboard [1], it is far from being all green. And do not give a look
for other architectures [2] than x86_64. And these breakages often
arise from an unrelated minor change.
On a side note, personally I am not convinced that moving fast (=
burning a lot of energy) is something helpful in the world context.
For instance, the same source version of a package as FreeCAD is
almost rebuilt daily [3] (and each build costs ~50min); aside a minor
change elsewhere can easily break it, I am not convinced it brings
something to rebuild it again and again. Well, I have mixed feelings
about this topic and indeed, we will have to think about it.
1: <http://ci.guix.gnu.org/eval/54803/dashboard>
2: <http://ci.guix.gnu.org/eval/54803/dashboard?system=i686-linux>
3: <https://data.guix.gnu.org/repository/1/branch/master/package/freecad/output-history>
Cheers,
simon
next prev parent reply other threads:[~2022-12-20 15:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 18:40 [bug#60042] [PATCH] gnu: git: Update to 2.39.0 Greg Hogan
2022-12-15 11:35 ` zimoun
2022-12-15 18:55 ` bug#60042: " Greg Hogan
2022-12-20 14:52 ` [bug#60042] " Ludovic Courtès
2022-12-20 15:38 ` Simon Tournier [this message]
2022-12-23 23:51 ` [bug#60042] Julia dependency on Git Ludovic Courtès
2022-12-30 13:15 ` zimoun
2023-01-03 17:59 ` Leo Famulari
2023-01-06 22:55 ` [bug#60042] What to call pinned package versions Ludovic Courtès
2023-01-09 10:32 ` Simon Tournier
2023-01-11 13:19 ` Simon Tournier
2023-01-11 17:27 ` Ludovic Courtès
2023-01-11 17:26 ` Ludovic Courtès
2023-01-26 16:45 ` zimoun
2022-12-20 16:38 ` [bug#60042] [PATCH] gnu: git: Update to 2.39.0 Greg Hogan
2022-12-25 16:18 ` Ludovic Courtès
2023-02-17 15:55 ` [bug#60042] open branches with target merge dates (was Re: [bug#60042] [PATCH] gnu: git: Update to 2.39.0.) Simon Tournier
2023-02-20 11:02 ` Ludovic Courtès
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=CAJ3okZ3j+HTATsoGE978b+LGk0KAEM7-BAGSy_Gtm61FzTWwQA@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=60042@debbugs.gnu.org \
--cc=code@greghogan.com \
--cc=ludo@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).