From: Jack Hill <jackhill@jackhill.us>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <Guix-devel@gnu.org>
Subject: Re: Let’s merge ‘core-updates’!
Date: Fri, 27 Sep 2019 18:56:07 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.20.1909271855250.15057@marsh.hcoop.net> (raw)
In-Reply-To: <87zhiuksyx.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 430 bytes --]
On Tue, 24 Sep 2019, Ludovic Courtès wrote:
> The ‘core-updates’ branch is in a good shape now, and I think we should
> go ahead and merge in the coming days!
>
> Please try to upgrade your system and your user profile to see if
> anything’s wrong for you (I did that a few days ago and I’m happy!).
I've tried this and I turned up a build problem with dconf-editor:
https://issues.guix.gnu.org/issue/37503
Best,
Jack
next prev parent reply other threads:[~2019-09-27 22:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 8:18 Let’s merge ‘core-updates’! Ludovic Courtès
2019-09-24 10:51 ` zimoun
2019-09-27 20:44 ` Ricardo Wurmus
2019-10-01 9:30 ` zimoun
2019-10-02 12:59 ` Ludovic Courtès
2019-10-02 15:40 ` zimoun
2019-09-24 13:06 ` Mikhail Kryshen
2019-09-28 21:12 ` Ludovic Courtès
2019-09-29 5:25 ` Mikhail Kryshen
2019-09-29 11:58 ` Marius Bakke
2019-09-29 14:01 ` John Soo
2019-09-29 14:40 ` Marius Bakke
2019-09-29 14:42 ` John Soo
2019-09-29 14:51 ` Marius Bakke
2019-09-27 18:50 ` pelzflorian (Florian Pelz)
2019-09-27 19:37 ` pelzflorian (Florian Pelz)
2019-09-27 22:01 ` Ricardo Wurmus
2019-09-27 20:43 ` Ricardo Wurmus
2019-09-27 22:56 ` Jack Hill [this message]
2019-09-28 11:00 ` Jelle Licht
2019-09-28 23:14 ` Kei Kebreau
2019-09-29 15:32 ` Kei Kebreau
2019-09-30 13:46 ` John Soo
2019-09-28 12:10 ` Konrad Hinsen
2019-10-02 12:57 ` Ludovic Courtès
2019-10-02 13:01 ` Ludovic Courtès
2019-10-02 13:15 ` Marius Bakke
2019-10-06 9:56 ` Ludovic Courtès
2019-10-08 9:48 ` ‘core-updates’ merged! 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=alpine.DEB.2.20.1909271855250.15057@marsh.hcoop.net \
--to=jackhill@jackhill.us \
--cc=Guix-devel@gnu.org \
--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).