From: Leo Famulari <leo@famulari.name>
To: Alex Sassmannshausen <alex.sassmannshausen@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH 0/3] Add a generalized `wrap-language-programs`
Date: Fri, 18 Nov 2016 03:34:37 -0500 [thread overview]
Message-ID: <20161118083437.GB10225@jasmine> (raw)
In-Reply-To: <87a8cxnrlp.fsf@gmail.com>
On Fri, Nov 18, 2016 at 09:02:10AM +0100, Alex Sassmannshausen wrote:
> Leo Famulari writes:
> > Changes like this will need to go on the core-updates branch, where we
> > make changes to the core of the system.
>
> Makes sense, I will push it to core-updates tonight.
To clarify, I didn't read all the patches yet, and I'm not the best
person to review them. I was just trying to explain why it might take a
long time to test this kind of change.
next prev parent reply other threads:[~2016-11-18 8:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 13:27 [PATCH 0/3] Add a generalized `wrap-language-programs` Alex Sassmannshausen
2016-11-16 13:27 ` [PATCH 1/3] build/utils: Add `wrap-language-programs` Alex Sassmannshausen
2016-11-18 23:07 ` Ludovic Courtès
2016-11-16 13:27 ` [PATCH 2/3] build/perl-build-system: Add `wrap` phase Alex Sassmannshausen
2016-11-16 13:27 ` [PATCH 3/3] build/python-build-system: Refactor `wrap` Alex Sassmannshausen
[not found] ` <582C6035.1070202@crazy-compilers.com>
2016-11-17 15:58 ` [PATCH 0/3] Add a generalized `wrap-language-programs` Alex Sassmannshausen
2016-11-17 17:09 ` Alex Sassmannshausen
2016-11-17 17:16 ` Hartmut Goebel
2016-11-17 21:15 ` Leo Famulari
2016-11-18 8:02 ` Alex Sassmannshausen
2016-11-18 8:34 ` Leo Famulari [this message]
2016-11-18 9:07 ` Alex Sassmannshausen
2016-11-18 8:41 ` Hartmut Goebel
2016-11-18 9:10 ` Ludovic Courtès
2016-11-18 15:16 ` Alex Sassmannshausen
2016-11-18 22:52 ` Ludovic Courtès
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=20161118083437.GB10225@jasmine \
--to=leo@famulari.name \
--cc=alex.sassmannshausen@gmail.com \
--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).