From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+willy=40w.ods.org-S262809AbVGKV6h@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S262809AbVGKV6h (ORCPT <rfc822;willy@w.ods.org>);
	Mon, 11 Jul 2005 17:58:37 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262811AbVGKV4L
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Mon, 11 Jul 2005 17:56:11 -0400
Received: from ns.snowman.net ([66.92.160.21]:28312 "EHLO ns.snowman.net")
	by vger.kernel.org with ESMTP id S262801AbVGKVz4 (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Mon, 11 Jul 2005 17:55:56 -0400
Date: Mon, 11 Jul 2005 17:56:03 -0400
From: Stephen Frost <sfrost@snowman.net>
To: Marc Aurele La France <tsi@ualberta.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel header policy
Message-ID: <20050711215603.GE24207@ns.snowman.net>
Mail-Followup-To: Marc Aurele La France <tsi@ualberta.ca>,
	linux-kernel@vger.kernel.org
References: <Pine.BSO.4.61.0507111533340.23021@login3.srv.ualberta.ca>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="gW8DBBCIxbs/VBqt"
Content-Disposition: inline
In-Reply-To: <Pine.BSO.4.61.0507111533340.23021@login3.srv.ualberta.ca>
X-Editor: Vim http://www.vim.org/
X-Info: http://www.snowman.net
X-Operating-System: Linux/2.4.24ns.3.0 (i686)
X-Uptime: 17:52:59 up 30 days, 14:12,  7 users,  load average: 0.04, 0.04, 0.06
User-Agent: Mutt/1.5.9i
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org


--gW8DBBCIxbs/VBqt
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

* Marc Aurele La France (tsi@ualberta.ca) wrote:
> To that end, I would propose, as a possible technical solution, extending
> the kernel build process to detect these errors during kernel development.

Well, couple stupid comments:

#1: I'm not *entirely* sure Linus reads every mail to lkml..  Dunno if
    you also sent it to him directly, but if not then that might explain
    the lack of response...

#2: Have you got a patch that does this?  If not, you might want to
    write one up and just submit it..  If you're expecting someone else
    to write it, well, that might also be why you've not had much
    response... :)

    	Thanks,

		Stephen

--gW8DBBCIxbs/VBqt
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

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

iD8DBQFC0urzrzgMPqB3kigRAsRYAJ9Jm6AMsemgScgN3Q1UdiBBpGGIOwCfQV66
l2QtNr0fjZf56lL2bOcesdA=
=n56/
-----END PGP SIGNATURE-----

--gW8DBBCIxbs/VBqt--