Received: from spf1.us4.outblaze.com (spf1.us4.outblaze.com [205.158.62.23]) by sdf.lonestar.org (8.12.10/8.12.10) with ESMTP id j0V3jgnM016062 for ; Mon, 31 Jan 2005 03:45:43 GMT Received: from lists.gnu.org (lists.gnu.org [199.232.76.165]) by spf1.us4.outblaze.com (Postfix) with ESMTP id 5701929853C for ; Mon, 31 Jan 2005 03:46:22 +0000 (GMT) Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CvSif-0008Ur-3e for migo@homemail.com; Sun, 30 Jan 2005 22:59:21 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1CvSha-0008O7-Le for gnu-arch-users@gnu.org; Sun, 30 Jan 2005 22:58:15 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1CvShP-0008Fq-Af for gnu-arch-users@gnu.org; Sun, 30 Jan 2005 22:58:04 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CvShP-0008El-81 for gnu-arch-users@gnu.org; Sun, 30 Jan 2005 22:58:03 -0500 Received: from [83.216.134.182] (helo=cyclone.suffields.me.uk) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CvSON-00076l-72 for gnu-arch-users@gnu.org; Sun, 30 Jan 2005 22:38:25 -0500 Received: from asuffield by cyclone.suffields.me.uk with local (Exim 3.36 #1 (Debian)) id 1CvRzv-0006VI-00 for ; Mon, 31 Jan 2005 03:13:07 +0000 Date: Mon, 31 Jan 2005 03:13:07 +0000 From: Andrew Suffield To: gnu-arch-users@gnu.org Subject: Re: [Gnu-arch-users] What's the rationale behind the cmd-build-config.c restrictions? Message-ID: <20050131031307.GC24728@suffields.me.uk> Mail-Followup-To: gnu-arch-users@gnu.org References: <87zmyu50ym.fsf@trouble.defaultvalue.org> <87mzut5l5k.fsf@flame.org> <87oef6zwp5.fsf@trouble.defaultvalue.org> Mime-Version: 1.0 In-Reply-To: <87oef6zwp5.fsf@trouble.defaultvalue.org> X-No-CC: I subscribe to this list; do not CC me on replies. User-Agent: Mutt/1.5.6+20040907i X-BeenThere: gnu-arch-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: a discussion list for all things arch-ish List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1282225502==" Sender: gnu-arch-users-bounces+migo=homemail.com@gnu.org Errors-To: gnu-arch-users-bounces+migo=homemail.com@gnu.org Status: RO Content-Length: 1577 Lines: 58 --===============1282225502== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="WfZ7S8PLGjBY9Voh" Content-Disposition: inline --WfZ7S8PLGjBY9Voh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 30, 2005 at 10:52:06AM -0600, Rob Browning wrote: > Of course, there may be good reasons for not allowing some or all of > this, which is why I raised the original question. Nah. Historically it used to mean something else in that argument. Now it's just a filename with a search path, only it was never quite fixed properly. --=20 .''`. ** Debian GNU/Linux ** | Andrew Suffield : :' : http://www.debian.org/ | `. `' | `- -><- | --WfZ7S8PLGjBY9Voh Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFB/aJDlpK98RSteX8RAjyHAJ9VW8ITJwzc7HUODiSY6axlG2fCpwCfZaGK s6r+xjVxfFq8Th7rwngecJ8= =oElH -----END PGP SIGNATURE----- --WfZ7S8PLGjBY9Voh-- --===============1282225502== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Gnu-arch-users mailing list Gnu-arch-users@gnu.org http://lists.gnu.org/mailman/listinfo/gnu-arch-users GNU arch home page: http://savannah.gnu.org/projects/gnu-arch/ --===============1282225502==--