unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: 01/01: gnu: gnurl: Update to 7.44.0.
Date: Sun, 18 Oct 2015 20:07:22 +0300	[thread overview]
Message-ID: <20151018200722.0b9926bf@debian-netbook> (raw)
In-Reply-To: <876124i15h.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 887 bytes --]

On Sun, 18 Oct 2015 18:36:58 +0200
ludo@gnu.org (Ludovic Courtès) wrote:

> Andreas Enge <andreas@enge.fr> skribis:
> 
> > I have also updated curl to 7.45.0.
> >
> > $ guix refresh -l curl
> > Building the following 82 packages would ensure 142 dependent
> > packages...  
> 
> Sounds OK to me.
> 
> > Is it okay to push to master, or should I wait for the next core-updates
> > cycle?  
> 
> ‘core-updates’ is for updates of the core: libc, gcc, coreutils, GMP,
> etc.  Here that would be a ‘curl-update’ or something like that.
> 
> Ludo’.

The concern is more about the numbers of packages that would be rebuilt from
pushing the update

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-10-18 17:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20151018101335.23039.16829@vcs.savannah.gnu.org>
     [not found] ` <E1Znky8-00060X-9c@vcs.savannah.gnu.org>
2015-10-18 10:26   ` 01/01: gnu: gnurl: Update to 7.44.0 Andreas Enge
2015-10-18 10:39     ` Efraim Flashner
2015-10-18 16:36     ` Ludovic Courtès
2015-10-18 17:07       ` Efraim Flashner [this message]
2015-10-19 14:59         ` Ludovic Courtès
2015-10-20 16:18       ` Andreas Enge

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=20151018200722.0b9926bf@debian-netbook \
    --to=efraim@flashner.co.il \
    --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).