From: Marius Bakke <mbakke@fastmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>, "Andreas Enge" <andreas@enge.fr>
Cc: 30441@debbugs.gnu.org
Subject: [bug#30441] [PATCH] gnu: boost: Update to 1.66.0.
Date: Tue, 27 Feb 2018 14:49:12 +0100 [thread overview]
Message-ID: <87k1uyv8yv.fsf@fastmail.com> (raw)
In-Reply-To: <87woyy4w3l.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 810 bytes --]
Ludovic Courtès <ludo@gnu.org> writes:
> Hello,
>
> Andreas Enge <andreas@enge.fr> skribis:
>
>> On Tue, Feb 13, 2018 at 02:46:33PM -0500, Leo Famulari wrote:
>>> This is a change for the next core-updates cycle, so I put it on my
>>> local core-updates-next branch. But please try to remember it, too :)
>>
>> would it not be better to build it (after the next core-updates merge,
>> or even the next release) on a feature branch?
>
> I’d recommend either that or current ‘staging’ (though you’d need to
> check with Leo and Marius if that’s fine) or ‘core-updates’.
Current 'staging' is almost built, so it would have to be the next round.
Also, Boost has ~1400 dependents, so it's a bit heavy even for 'staging'.
Let's try to do a new 'core-updates' soonish instead.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-02-27 13:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 23:33 [bug#30441] [PATCH] gnu: boost: Update to 1.66.0 Arun Isaac
2018-02-13 19:46 ` Leo Famulari
2018-02-14 6:20 ` Arun Isaac
2018-02-17 13:58 ` Andreas Enge
2018-02-27 9:31 ` Ludovic Courtès
2018-02-27 13:49 ` Marius Bakke [this message]
2018-02-27 14:22 ` Ludovic Courtès
2018-06-22 15:59 ` bug#30441: " Gábor Boskovits
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=87k1uyv8yv.fsf@fastmail.com \
--to=mbakke@fastmail.com \
--cc=30441@debbugs.gnu.org \
--cc=andreas@enge.fr \
--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).