Date: Tue, 11 Dec 2001 02:20:47 -0700 From: Warner Losh <imp@harmony.village.org> To: Sheldon Hearn <sheldonh@starjuice.net> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/usb usbdevs.h usbdevs_data.h Message-ID: <200112110920.fBB9KlM25819@harmony.village.org> In-Reply-To: Your message of "Mon, 10 Dec 2001 13:55:45 %2B0200." <57664.1007985345@axl.seasidesoftware.co.za> References: <57664.1007985345@axl.seasidesoftware.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <57664.1007985345@axl.seasidesoftware.co.za> Sheldon Hearn writes: : > Modified files: : > sys/dev/usb usbdevs.h usbdevs_data.h : > Log: : > Regen from usbdevs rev 1.70: added some AGFA scanners : : This is the first time I've handled changes to usbdevs, and I must say : it's a real PITA. 4 commits to apply a single patch to HEAD and then : merge onto RELENG_4. : : Is it really worth it, just to show the version of usbdevs from which : the generated files were derived? Can't people just get that : information from the CVS logs? I do the same thing with the pccarddevs, and it isn't that big of a pain. It is useful to have, and often points out mistakes people have made. Someone threatened to rewrite all this stuff a long time ago, but that never appeared. It is too painful from my experimentation with pccarddevs to generate on the fly all the time. I also tend to commit both pccarddevs and pccardevs*.h on one commit on MFC, but there haven't been too many of them. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200112110920.fBB9KlM25819>