From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Core-updates timeline (was: Re: [PATCH 2/2] gnu: perl: Enable threading support.)
Date: Sat, 1 Oct 2016 12:40:49 -0400 [thread overview]
Message-ID: <20161001164049.GD1499@jasmine> (raw)
In-Reply-To: <8760pci4pv.fsf@gnu.org>
On Sat, Oct 01, 2016 at 03:22:36PM +0200, Ludovic Courtès wrote:
> I pushed simplified versions of these two patches as
> 56ee1d2015e9b2c55d34f19c70b06eefe8a20c76 and
> 156c0810e936413ac554e2883343b3b40695cfdc.
>
> I think this was the last non-bug-fix change for this core-updates
> cycle. :-)
Cool :)
I've been waiting for libarchive 3.2.2 [0] so that I can graft it on
master and ungraft it on core-updates. But, I can try cherry-picking the
most important changes today. When do you hope to freeze core-updates?
Do you want me to try cherry-picking?
https://github.com/libarchive/libarchive/milestone/4
next prev parent reply other threads:[~2016-10-01 16:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 4:56 [PATCH 0/2] Perl: Enable threading support Ben Woodcroft
2016-09-20 4:56 ` [PATCH 1/2] gnu: perl: Split configure phase Ben Woodcroft
2016-09-24 5:02 ` Ludovic Courtès
2016-09-20 4:56 ` [PATCH 2/2] gnu: perl: Enable threading support Ben Woodcroft
2016-09-24 5:05 ` Ludovic Courtès
2016-09-26 10:03 ` Ben Woodcroft
2016-10-01 13:22 ` Ludovic Courtès
2016-10-01 16:40 ` Leo Famulari [this message]
2016-10-02 13:38 ` Core-updates timeline Ludovic Courtès
2016-10-02 18:50 ` Leo Famulari
2016-10-02 20:14 ` libarchive security fixes (was Re: Core-updates timeline) Leo Famulari
2016-10-03 16:10 ` Ludovic Courtès
2016-10-03 18:14 ` Leo Famulari
2016-10-07 20:16 ` Core-updates timeline Ludovic Courtès
2016-09-20 20:58 ` [PATCH 0/2] Perl: Enable threading support Eric Bavier
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=20161001164049.GD1499@jasmine \
--to=leo@famulari.name \
--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 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.