From owner-freebsd-current@FreeBSD.ORG Wed Sep 29 08:41:46 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 38AC616A4CE for ; Wed, 29 Sep 2004 08:41:46 +0000 (GMT) Received: from ctb-mesg3.saix.net (ctb-mesg3.saix.net [196.25.240.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id BEB7443D2F for ; Wed, 29 Sep 2004 08:41:45 +0000 (GMT) (envelope-from sheldonh@starjuice.net) Received: from urchin.seasidesoftware.co.za (wbs-208-167.telkomadsl.co.za [165.165.208.167]) by ctb-mesg3.saix.net (Postfix) with ESMTP id C5EBC26C4; Wed, 29 Sep 2004 10:41:41 +0200 (SAST) Received: from axl.seasidesoftware.co.za ([10.0.0.2]) by urchin.seasidesoftware.co.za with esmtp (Exim 4.34) id 1CCa1t-000OSL-JM; Wed, 29 Sep 2004 10:41:41 +0200 From: Sheldon Hearn To: Mike Tancsa In-Reply-To: <6.1.2.0.0.20040928145711.09c0d7c8@64.7.153.2> References: <6.1.2.0.0.20040928145711.09c0d7c8@64.7.153.2> Content-Type: text/plain Message-Id: <1096447301.22745.14.camel@axl.seasidesoftware.co.za> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 29 Sep 2004 10:41:41 +0200 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Wed, 29 Sep 2004 11:54:18 +0000 cc: freebsd-current@freebsd.org Subject: Re: /usr/share/misc/pci_vendors X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Sep 2004 08:41:46 -0000 On Tue, 2004-09-28 at 21:21, Mike Tancsa wrote: > Any chance of updating the pci_vendors file in HEAD and RELENG_5 ? There > is a rather odd entry for 14F1 which should be > Conexant Systems, Inc > > according to http://www.pcidatabase.com/reports.php?type=tab-delimeted > > But in FreeBSD, it says > > 14F1 Zuhair mohammed Saeed Manual changes get blown away by the next automated merge from the two sources we use. So we need to try get this fixed in the offending upstream source. Actually, that seems to have been a transient flake in one of them. It doesn't appear in either one now. I'll ask RE for permission to sync up. Thanks, Sheldon.