huge file drivers/scsi/aic78xx/CHANGELOG in 2.4.21-rc7?
Do we really need 23000 lines of "perforce describe" output in the kernel source tree?
drivers/scsi/aic79xx/CHANGELOG 2003-06-03 16:05:55.000000000 +0000 renamed from drivers/scsi/aic79xx/CHANGELOG 1970-01-01 00:00:00.000000000 +0000 +15 -0
@@ -0,0 +1,23260 @@ +Change 1861 by scottl@scottl-template on 2003/01/21 18:26:00 + + Update driver version to 1.3.0 + +Affected files ... + +... //depot/aic7xxx/linux/drivers/scsi/aic7xxx/aic79xx_osm.h#108 edit +... //depot/linux_mod_devel/scsi.aic79xx/rpm/aic79xx.spec#25 edit +... //depot/linux_mod_devel/scsi.aic79xx/rpm/install.sh#28 edit + +Change 1859 by scottl@scottl-template on 2003/01/21 15:27:08 + + readme.txt: + README.aic7xxx: + Convert tabs to spaces.
...
Signature · 3 lines
Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045
Quoted 2 lines · --On Saturday, June 07, 2003 23:11:23 -0700 Dan Kegel <[email protected]> wrote:
Do we really need 23000 lines of "perforce describe" output in the kernel source tree?
The CHANGELOG has never been in the BK files that I submit. My guess is that when the driver was last updated, the CHANGELOG file from the tar distribution was included. I don't think it should be especially if the BK files are used for the next update. In my merges with 2.4.X, I have maintained file history even when duplicate changes were integrated via "patch" instead of via BK.
--
Justin