From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Rebuilds and branches
Date: Sun, 12 Oct 2014 14:58:36 +0200 [thread overview]
Message-ID: <87zjd1zbpf.fsf_-_@gnu.org> (raw)
In-Reply-To: <87tx39yjxk.fsf@netris.org> (Mark H. Weaver's message of "Sun, 12 Oct 2014 00:46:15 -0400")
Mark H Weaver <mhw@netris.org> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Eric Bavier <ericbavier@gmail.com> skribis:
>>
>>> From 88a4cc3aa53c73186b5dbb85bf03b2138f24c825 Mon Sep 17 00:00:00 2001
>>> From: Eric Bavier <bavier@member.fsf.org>
>>> Date: Fri, 10 Oct 2014 13:07:55 -0500
>>> Subject: [PATCH 2/4] gnu: libjpeg: Upgrade to version 9a.
>>>
>>> * gnu/packages/image.scm (libjpeg): Upgrade to version 9a.
>>
>> OK.
>
> This triggered over 450 rebuilds. I wonder if it should have been done
> in core-updates instead.
Arf, probably yes, in a ‘libjpeg-update’ branch, rather.
What about having a policy for that? Like, above some threshold of the
number of rebuilds reported by ‘guix refresh -l’ (200 packages?), set up
a separate branch and Hydra job set.
In an ideal world a patch queue manager would automatically take care of
that.
Ludo’.
next prev parent reply other threads:[~2014-10-12 12:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 18:18 [PATCH 2/4] gnu: libjpeg: Upgrade to version 9a Eric Bavier
2014-10-11 21:59 ` Ludovic Courtès
2014-10-12 4:46 ` Mark H Weaver
2014-10-12 12:58 ` Ludovic Courtès [this message]
2014-10-12 14:50 ` Rebuilds and branches Mark H Weaver
2014-10-12 15:58 ` 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=87zjd1zbpf.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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).