From: Andreas Enge <andreas@enge.fr>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 2/3] gnu: Don't use guix build utils
Date: Thu, 18 Feb 2016 20:55:05 +0100 [thread overview]
Message-ID: <20160218195505.GB3445@solar> (raw)
In-Reply-To: <20160218001523.GB26345@jasmine>
On Wed, Feb 17, 2016 at 07:15:23PM -0500, Leo Famulari wrote:
> The commit that removes the module only makes sense in the context of
> adding vcsh. It's analogous to adding a module that is required for a
> new package, and that is done in a single commit. So, I think it's
> better to squash the commits.
Yes, I agree it could/should be done at the same time as adding vcsh.
First of all, we will need to get perl-shell-command in; I do not find
the patch any more. Leo, if you still have it and it looks good, could
you please push it? Otherwise, Christopher, could you resend it?
Sorry for my lack of organisation,
Andreas
next prev parent reply other threads:[~2016-02-18 19:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-13 16:07 [PATCH] gnu: Add vcsh and perl-shell-command Christopher Baines
2016-02-13 16:07 ` [PATCH 1/3] gnu: Add perl-shell-command Christopher Baines
2016-02-13 22:42 ` Leo Famulari
2016-02-13 16:07 ` [PATCH 2/3] gnu: Don't use guix build utils Christopher Baines
2016-02-13 22:39 ` Leo Famulari
2016-02-17 18:28 ` Christopher Baines
2016-02-18 0:15 ` Leo Famulari
2016-02-18 19:55 ` Andreas Enge [this message]
2016-02-18 19:59 ` Christopher Baines
2016-02-18 20:16 ` Andreas Enge
2016-02-18 21:13 ` Christopher Baines
2016-02-18 21:37 ` Andreas Enge
2016-02-13 16:07 ` [PATCH 3/3] gnu: Add vcsh Christopher Baines
2016-02-13 22:41 ` Leo Famulari
2016-02-14 20:36 ` Christopher Baines
2016-02-17 18:11 ` Andreas Enge
2016-02-17 18:59 ` Christopher Baines
2016-02-18 0:11 ` Leo Famulari
2016-02-18 0:27 ` Christopher Baines
2016-02-18 20:01 ` Andreas Enge
2016-02-18 21:04 ` Christopher Baines
2016-02-18 21:26 ` Leo Famulari
2016-02-18 21:32 ` Christopher Baines
2016-02-18 21:39 ` 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=20160218195505.GB3445@solar \
--to=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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).