all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org, Dika Setya Prayogi <dikasetyaprayogi@gmail.com>
Subject: Re: guixsd offline installation media
Date: Fri, 18 Dec 2015 21:11:38 +0100	[thread overview]
Message-ID: <20151218201138.GA30822@thebird.nl> (raw)
In-Reply-To: <87vb7vhcxk.fsf@netris.org>

Hi Mark,

On Fri, Dec 18, 2015 at 12:41:27PM -0500, Mark H Weaver wrote:
> Pjotr Prins <pjotr.public12@thebird.nl> writes:
> 
> > If it is technically feasibly it would be a great feature to go back
> > in time without resorting to using a checkout of the guix source tree
> > :)
> 
> I'm not sure why using a git checkout should be considered an
> unfortunate thing to have to resort to.  To my mind, it is precisely the
> right tool for the job, and far more flexible and efficient than using
> "guix pull".  It is the way I've been using 'guix' from the beginning.
> I recommend giving it a try some time :)

I use git *all* the time. No issue with that.

I don't think we can ask that from most users.

We are talking reproducible deployment here.

Pj.

  reply	other threads:[~2015-12-18 20:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-16  4:07 guixsd offline installation media Dika Setya Prayogi
2015-12-16  4:42 ` Pjotr Prins
2015-12-16  4:57   ` Pjotr Prins
2015-12-17 22:35     ` Ludovic Courtès
2015-12-18  3:40       ` Pjotr Prins
2015-12-18 17:41         ` Mark H Weaver
2015-12-18 20:11           ` Pjotr Prins [this message]
2015-12-19 14:09           ` ‘guix pull’ vs. Git Ludovic Courtès
2015-12-17 22:41 ` guixsd offline installation media Ludovic Courtès
2015-12-18  8:03   ` Dika Setya Prayogi
2015-12-18  9:19     ` Pjotr Prins
2015-12-20 12:08       ` Efraim Flashner
2015-12-23 10:12         ` Alex Vong

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=20151218201138.GA30822@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --cc=dikasetyaprayogi@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=mhw@netris.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.