unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nils Gillmann <ng0@n0.is>
To: guix-devel@gnu.org
Subject: Re: preparing the next release v0.15.0
Date: Wed, 20 Jun 2018 20:33:02 +0000	[thread overview]
Message-ID: <20180620203302.7e4ql5srmnt4ol5m@abyayala> (raw)
In-Reply-To: <87bmc55mmh.fsf@posteo.net>

Is it worth mentioning that guix pull for some time now
is back to relatively decent 1GB RAM consumption? I
think I had it even succeed on 512MB RAM per handwritten
notes here, but I haven't had the possibility to test again
on low specs.

  reply	other threads:[~2018-06-20 20:32 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-13 21:07 preparing the next release v0.15.0 Ricardo Wurmus
2018-06-14  5:46 ` Pjotr Prins
2018-06-14  8:24   ` Ricardo Wurmus
2018-06-14 19:46     ` Pierre Neidhardt
2018-06-15  9:42     ` Ludovic Courtès
2018-06-14  9:14   ` Clément Lassieur
2018-07-02  9:44     ` Ludovic Courtès
2018-07-02 15:25       ` Efraim Flashner
2018-07-03 19:43         ` Ludovic Courtès
2018-07-03 20:24           ` Ricardo Wurmus
2018-07-04  7:28           ` Ludovic Courtès
2018-07-02 15:29       ` Nils Gillmann
2018-06-15  9:53 ` Ludovic Courtès
2018-06-15 13:11   ` Ricardo Wurmus
2018-06-18 20:31 ` Ricardo Wurmus
2018-06-18 22:44   ` Pierre Neidhardt
2018-06-19  1:49   ` Kei Kebreau
2018-06-19  7:25   ` Gábor Boskovits
2018-06-19 12:36   ` Marius Bakke
2018-06-19 12:48     ` Julien Lepiller
2018-06-19 14:32       ` swedebugia
2018-06-20 20:45       ` Ricardo Wurmus
2018-06-20 18:38     ` Kei Kebreau
2018-06-20 20:33       ` Nils Gillmann [this message]
2018-06-20 21:10         ` Ludovic Courtès
2018-06-21  1:05           ` Kei Kebreau
2018-06-21 10:45             ` Ricardo Wurmus
2018-06-20 21:11       ` Marius Bakke
2018-06-20 21:55       ` swedebugia
2018-06-21  1:06         ` Kei Kebreau

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=20180620203302.7e4ql5srmnt4ol5m@abyayala \
    --to=ng0@n0.is \
    --cc=guix-devel@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).