From mboxrd@z Thu Jan  1 00:00:00 1970
From: John Darrington <john@darrington.wattle.id.au>
Subject: Re: Cross-compilation fixes
Date: Sat, 14 Dec 2013 18:22:56 +0100
Message-ID: <20131214172255.GA1707@intra>
References: <20131214150609.GA10980@intra>
 <877gb7wew6.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="mYCpIKhGyMATD0i+"
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:52262)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <john@darrington.wattle.id.au>) id 1Vrsvf-0000rW-So
	for guix-devel@gnu.org; Sat, 14 Dec 2013 12:23:08 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <john@darrington.wattle.id.au>) id 1Vrsvb-0002gC-M3
	for guix-devel@gnu.org; Sat, 14 Dec 2013 12:23:03 -0500
Content-Disposition: inline
In-Reply-To: <877gb7wew6.fsf@gnu.org>
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
To: Ludovic =?iso-8859-1?Q?Court=E8s?= <ludo@gnu.org>
Cc: guix-devel@gnu.org


--mYCpIKhGyMATD0i+
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Dec 14, 2013 at 05:55:53PM +0100, Ludovic Court=C3=A8s wrote:
     John Darrington <john@darrington.wattle.id.au> skribis:
    =20
     > Attached are several patches addressing cross-compilation issues,
     > culminating in a large patch affecting lots of files, moving=20
     > various "inputs" to "native-inputs".
    =20
     Could you send them inline, one message per patch?  That would
     significantly ease review.

I'll see what I can do.
    =20
     (=E2=80=98git format-patch=E2=80=99 and =E2=80=98git send-email=E2=80=
=99 can be used for that, as noted
     in HACKING.)

I can't find any mention of "git send-email" in HACKING, and there appears
to be no such command.  At least not in the git that I have installed (1.7.=
10.4)

J'

    =20

--=20
PGP Public key ID: 1024D/2DE827B3=20
fingerprint =3D 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.


--mYCpIKhGyMATD0i+
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlKsk+8ACgkQimdxnC3oJ7O+QwCePiELF4V2B+A1cnvYIqNbbt7Z
f5MAn1fkdPCSrFl/C20xjkjiSCVAlvqB
=czgC
-----END PGP SIGNATURE-----

--mYCpIKhGyMATD0i+--