From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+willy=40w.ods.org@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S264453AbTFPWSQ (ORCPT <rfc822;willy@w.ods.org>);
	Mon, 16 Jun 2003 18:18:16 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264454AbTFPWSQ
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Mon, 16 Jun 2003 18:18:16 -0400
Received: from pizda.ninka.net ([216.101.162.242]:1233 "EHLO pizda.ninka.net")
	by vger.kernel.org with ESMTP id S264453AbTFPWSP (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Mon, 16 Jun 2003 18:18:15 -0400
Date: Mon, 16 Jun 2003 15:27:45 -0700 (PDT)
Message-Id: <20030616.152745.124055059.davem@redhat.com>
To: girouard@us.ibm.com
Cc: stekloff@us.ibm.com, janiceg@us.ibm.com, jgarzik@pobox.com,
       kenistonj@us.ibm.com, lkessler@us.ibm.com, linux-kernel@vger.kernel.org,
       netdev@oss.sgi.com, niv@us.ibm.com
Subject: Re: patch for common networking error messages
From: "David S. Miller" <davem@redhat.com>
In-Reply-To: <OFF1F6B3DC.30C0E5DE-ON85256D47.007AEFAF@us.ibm.com>
References: <OFF1F6B3DC.30C0E5DE-ON85256D47.007AEFAF@us.ibm.com>
X-FalunGong: Information control.
X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

   From: Janice Girouard <girouard@us.ibm.com>
   Date: Mon, 16 Jun 2003 17:29:15 -0500
   
   For the sake of consistency and automatic error log analysis, it might be

And all the scripts checking for the existing messages
in log files?  Screw them, right?

This whole idea is starting to leave a very bad taste in
my mouth...