From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: Starting 'core-updates'
Date: Tue, 01 May 2018 22:46:48 +0200 [thread overview]
Message-ID: <87lgd3nlxj.fsf@gnu.org> (raw)
In-Reply-To: <87zi1j5j6n.fsf@netris.org> (Mark H. Weaver's message of "Tue, 01 May 2018 14:23:28 -0400")
Mark H Weaver <mhw@netris.org> skribis:
> The reason that I moved my own systems so agressively to core-updates
> this cycle is because I no longer trust that grafting works properly on
> 'master', and so security flaws might not be fully addressed there. I'm
> disappointed that there have been so many delays since then, and I'd
> prefer not to add any more.
I agree, let’s not delay things further.
So option #1 + rhash, so be it! When you’ve done that Marius, I’m happy
to get ‘core-updates’ built on berlin.
Besides, what makes you think grafting doesn’t work properly on master?
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-05-01 20:46 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
2018-05-01 18:23 ` Mark H Weaver
2018-05-01 20:46 ` Ludovic Courtès [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lgd3nlxj.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 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.