From: ludo@gnu.org (Ludovic Courtès)
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] guxi: cmake-build-system: Enable output for failing test-cases.
Date: Mon, 17 Oct 2016 22:14:32 +0200 [thread overview]
Message-ID: <87shruka1j.fsf@gnu.org> (raw)
In-Reply-To: <58008FB7.7080101@crazy-compilers.com> (Hartmut Goebel's message of "Fri, 14 Oct 2016 09:56:39 +0200")
Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:
> Am 13.10.2016 um 22:12 schrieb Ludovic Courtès:
>> It’s a good idea, but it would entail a rebuild of 1,000+ packages. Can
>> you save it for the next big-rebuild cycle?
>
> No problem.
>
> Still have to learn what "next big-rebuild cycle" means. Is there a
> branch for it?
Not really!
Well there’s core-updates for changes that trigger a rebuild of 90% of
the packages, and then occasionally topic branches (‘python-updates’,
etc.)
Once ‘core-updates’ is merged (hopefully in a few days), we could start
a ‘staging’ branch and put changes that require between ~300 and ~1200
rebuilds. The idea would be to close the branch much more quickly than
core-updates (the changes should be less disruptive, with little chance
of breaking things.)
Ludo’.
next prev parent reply other threads:[~2016-10-17 20:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 13:02 [PATCH] guxi: cmake-build-system: Enable output for failing test-cases Hartmut Goebel
2016-10-13 20:12 ` Ludovic Courtès
2016-10-14 7:56 ` Hartmut Goebel
2016-10-17 20:14 ` Ludovic Courtès [this message]
2016-10-18 7:46 ` Hartmut Goebel
2016-10-18 12:41 ` Branching and rebuild scheduling strategy Ludovic Courtès
2016-11-15 21:13 ` [PATCH] guxi: cmake-build-system: Enable output for failing test-cases Leo Famulari
2016-11-15 21:44 ` Hartmut Goebel
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87shruka1j.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.