From: John Darrington <john@darrington.wattle.id.au>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, John Darrington <jmd@gnu.org>
Subject: Re: [PATCH] gnu: aegis: New variable.
Date: Thu, 17 Jul 2014 17:54:55 +0200 [thread overview]
Message-ID: <20140717155455.GA3678@intra> (raw)
In-Reply-To: <87r41kdo87.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]
On Thu, Jul 17, 2014 at 05:00:40PM +0200, Ludovic Courtès wrote:
> * gnu/packages/version-control.scm (aegis): New variable.
> * gnu/packages/patches/aegis-constness-error.patch: New file.
> * gnu/packages/patches/aegis-perl-tempdir1.patch: New file.
> * gnu/packages/patches/aegis-perl-tempdir2.patch: New file.
> * gnu/packages/patches/aegis-test-fixup-1.patch: New file.
> * gnu/packages/patches/aegis-test-fixup-2.patch: New file.
Could you merge tempdir1 and tempdir2, as well as fixup1 and fixup2?
I could do. But I'm hoping that upstream will apply these patches.
So I'd rather keep them separate so that their maintainers can consider them on a
case by case basis, and to make our lives easier should they decide to apply some
but not the others.
J'
--
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-07-17 15:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 13:47 [PATCH] gnu: aegis: New variable John Darrington
2014-07-17 15:00 ` Ludovic Courtès
2014-07-17 15:54 ` John Darrington [this message]
2014-07-17 23:12 ` Ludovic Courtès
2014-07-17 16:05 ` John Darrington
2014-07-17 23:15 ` Ludovic Courtès
2014-07-18 4:35 ` John Darrington
2014-07-18 12:42 ` Ludovic Courtès
2014-07-20 7:18 ` John Darrington
2014-07-20 13:50 ` Ludovic Courtès
2014-07-20 19:22 ` John Darrington
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=20140717155455.GA3678@intra \
--to=john@darrington.wattle.id.au \
--cc=guix-devel@gnu.org \
--cc=jmd@gnu.org \
--cc=ludo@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).