The trouble with firmware
Posted Jan 6, 2011 3:40 UTC (Thu) by JohnLenz
Parent article: The trouble with firmware
It is not enough to just have the new firmware filenames in the HEAD of the Git repository, Oliva and Stallman would like to eliminate references to the original filenames (and the firmware files themselves) from the repository history. But they also would like to be able to pull from Linus Torvalds's mainline tree periodically.
If you do this, doesn't git recompute the sha1 hashes for the commit id for all future commits, since the sha1 of the parent is included in the current commit? So changing one entry in the history will ripple sha1 hash changes throughout the whole tree.
If so, this sounds like a bad idea. If you report a bug on linux-kernel and someone says "This is fixed in 4d5227500c8f ...", that sha1 hash won't be in your tree, the same commit will be referenced with some other hash. Also, if do a git bisect, you won't be able to report it because the hashes from your git bisect won't match with what you need to report on linux-kernel.
I suppose you could keep around a map between Linus's sha1 and your sha1 ids and remember to convert whenever you send email to linux-kernel.
to post comments)