From: Leo Famulari <leo@famulari.name>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Starting 'core-updates'
Date: Tue, 1 May 2018 10:23:20 -0400 [thread overview]
Message-ID: <20180501142320.GA14610@jasmine.lan> (raw)
In-Reply-To: <87lgd3h3c5.fsf@fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 913 bytes --]
On Tue, May 01, 2018 at 04:12:42PM +0200, Marius Bakke wrote:
> I was running a bit late with my patches and pushed them to a separate
> branch before noticing the 'rhash' update on 'master'. Now there have
> been a couple of world-rebuilding commits on the 'core-updates-next'
> branch since, so I wonder how to move forward.
>
> * Start 'core-updates' as-is.
> * Pick all updates from the -next branch that won't rebuild the world
> (that is everything apart from "xz" and "file").
> * Take all the -next commits, remove the Perl graft, and do a new 'core'
> evaluation.
>
> Any preferences? Due to the "rhash" update, I suppose we can take
> anything from -next that depends on CMake also with option #1.
I haven't been paying attention this cycle. But if anyone has, then I
think it's best to do option 1 along with the rhash, since most of the
bug-fixing work will still be valid.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-05-01 14:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-21 7:54 Successfully running GNOME on core-updates + staging Mark H Weaver
2018-04-22 19:55 ` Ludovic Courtès
2018-04-23 18:13 ` Marius Bakke
2018-04-25 12:14 ` Ludovic Courtès
2018-04-25 13:23 ` Efraim Flashner
2018-05-01 14:12 ` Starting 'core-updates' Marius Bakke
2018-05-01 14:23 ` Leo Famulari [this message]
2018-05-01 18:23 ` Mark H Weaver
2018-05-01 20:46 ` Ludovic Courtès
2018-05-01 21:21 ` Mark H Weaver
-- strict thread matches above, loose matches on Subject: below --
2020-01-27 19:59 Starting 'core-updates'? Marius Bakke
2020-01-27 20:44 ` Pierre Neidhardt
2020-01-27 21:46 ` zimoun
2020-01-28 8:55 ` Mathieu Othacehe
2020-01-28 9:08 ` Christopher Baines
2020-01-28 10:47 ` Ludovic Courtès
2020-01-28 10:51 ` Ludovic Courtès
2020-01-31 19:48 ` Maxim Cournoyer
2020-02-13 15:18 ` Jan Nieuwenhuizen
2020-02-14 15:18 ` 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=20180501142320.GA14610@jasmine.lan \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.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).