From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Andy Wingo <wingo@igalia.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Allow for incremental upgrade from guile-2.0 to guile-next.
Date: Thu, 24 Mar 2016 18:02:55 +0100 [thread overview]
Message-ID: <8760wbkdvk.fsf@drakenvlieg.flower> (raw)
In-Reply-To: <87d1qknglk.fsf@igalia.com> (Andy Wingo's message of "Thu, 24 Mar 2016 14:35:51 +0100")
Andy Wingo writes:
>> Using Guile-2.0 and Guile-2.2 together is currently cumbersome,
>> esp. on Guix
> I would like to review and apply these first upstream. WDYT?
Yes, I would prefer that too, thanks! Anything I can do to help here?
> Of course if we are being too slow, doing it in Guix is fine too, but
> it's less good than getting review upstream first.
Yes, I was thinking that if having Guix packages available to test, even
if not merged, that could help. I assumed Guix and Guile friendly
enough to do the right thing either way.
Greetings, Jan
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl
prev parent reply other threads:[~2016-03-24 17:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 21:25 [PATCH] Allow for incremental upgrade from guile-2.0 to guile-next Jan Nieuwenhuizen
2016-03-24 13:35 ` Andy Wingo
2016-03-24 17:02 ` Jan Nieuwenhuizen [this message]
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=8760wbkdvk.fsf@drakenvlieg.flower \
--to=janneke@gnu.org \
--cc=guix-devel@gnu.org \
--cc=wingo@igalia.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).