From owner-freebsd-hackers@FreeBSD.ORG  Tue Apr  5 04:30:46 2011
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: hackers@freebsd.org
Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35])
	by hub.freebsd.org (Postfix) with ESMTP id 9DD38106564A
	for <hackers@freebsd.org>; Tue,  5 Apr 2011 04:30:46 +0000 (UTC)
	(envelope-from dougb@FreeBSD.org)
Received: from 65-241-43-5.globalsuite.net (hub.freebsd.org
	[IPv6:2001:4f8:fff6::36])
	by mx2.freebsd.org (Postfix) with ESMTP id 1335F14EEE9;
	Tue,  5 Apr 2011 04:30:45 +0000 (UTC)
Message-ID: <4D9A9AF5.9020807@FreeBSD.org>
Date: Mon, 04 Apr 2011 21:30:45 -0700
From: Doug Barton <dougb@FreeBSD.org>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US;
	rv:1.9.2.15) Gecko/20110319 Thunderbird/3.1.9
MIME-Version: 1.0
To: Garrett Cooper <yanegomi@gmail.com>
References: <20110404141016.GL71940@rincewind.paeps.cx>	<4D9A0836.7070403@FreeBSD.org>
	<BANLkTimRsadMU-ECstu5Jszt=mG+c3RW2g@mail.gmail.com>
In-Reply-To: <BANLkTimRsadMU-ECstu5Jszt=mG+c3RW2g@mail.gmail.com>
X-Enigmail-Version: 1.1.2
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: hackers@freebsd.org
Subject: Re: Updating PCI vendors database
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Apr 2011 04:30:46 -0000

On 04/04/2011 20:30, Garrett Cooper wrote:
> 1. People may have automation that depends on this output.

To the extent that they rely on information that is out of date, fixing 
this is a feature. However I cannot imagine that this would be much of 
an issue.

> 2. Some braindead SCMs may be problematic with this change (p4?*COUGH*).

Eh? I don't parse this.


Doug

-- 

	Nothin' ever doesn't change, but nothin' changes much.
			-- OK Go

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/