unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: 02/05: gnu: nss, nss-certs: Update to 3.29.3.
Date: Wed, 15 Mar 2017 17:26:15 +0100	[thread overview]
Message-ID: <87wpbq7bh4.fsf@gnu.org> (raw)
In-Reply-To: <87vara3cqc.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (Marius Bakke's message of "Wed, 15 Mar 2017 14:12:43 +0100")

Marius Bakke <mbakke@fastmail.com> skribis:

> Marius Bakke <mbakke@fastmail.com> writes:
>
>> Patch attached. I *think* the two values are for client and server
>> respectively, but will study the source and build logs some more to make
>> sure we're adjusting the right knobs.
>>
>> I suggest we try this on 'core-updates' if the patch is correct.
>
> The patch builds fine on x86_64, and I've verified that these are the
> correct settings by decreasing the values instead of increasing.
>
> What do you think? Should we check if 25s is high enough on
> 'core-updates' or push it directly to 'master'?

Good catch.

It might be best to push to ‘core-updates’ to focus our build
resources.  No strong opinion though.

Thanks!

Ludo’.

  reply	other threads:[~2017-03-15 16:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170313174039.25881.89989@vcs0.savannah.gnu.org>
     [not found] ` <20170313174040.C5C6B20CAB@vcs0.savannah.gnu.org>
2017-03-14  6:24   ` 02/05: gnu: nss, nss-certs: Update to 3.29.3 Mark H Weaver
2017-03-14  6:31     ` Mark H Weaver
2017-03-14  9:14     ` Marius Bakke
2017-03-14 21:02       ` Mark H Weaver
2017-03-14 21:27         ` Leo Famulari
2017-03-14 21:39           ` Marius Bakke
2017-03-14 21:59             ` Leo Famulari
2017-03-14 22:12               ` Marius Bakke
2017-03-15 13:12                 ` Marius Bakke
2017-03-15 16:26                   ` Ludovic Courtès [this message]
2017-03-15 17:04                     ` Marius Bakke
2017-03-15 18:42                   ` Mark H Weaver

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=87wpbq7bh4.fsf@gnu.org \
    --to=ludo@gnu.org \
    --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).