Date: Mon, 4 Apr 2011 21:36:21 -0700 From: Garrett Cooper <yanegomi@gmail.com> To: Doug Barton <dougb@freebsd.org> Cc: hackers@freebsd.org Subject: Re: Updating PCI vendors database Message-ID: <BANLkTinubeVBu3eCw-q3G9N=M9VpcYcpxQ@mail.gmail.com> In-Reply-To: <4D9A9AF5.9020807@FreeBSD.org> References: <20110404141016.GL71940@rincewind.paeps.cx> <4D9A0836.7070403@FreeBSD.org> <BANLkTimRsadMU-ECstu5Jszt=mG%2Bc3RW2g@mail.gmail.com> <4D9A9AF5.9020807@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Apr 4, 2011 at 9:30 PM, Doug Barton <dougb@freebsd.org> wrote: > 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. perforce doesn't always grok large changes (especially deletions -- it gets ditzy). The last change that was committed by someone at $WORK to this file was several thousand lines long, and that was just additions IIRC. Thanks, -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BANLkTinubeVBu3eCw-q3G9N=M9VpcYcpxQ>