> 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.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/