Finding a patch's kernel version with git
Posted Jun 18, 2010 11:11 UTC (Fri) by farnz
In reply to: Finding a patch's kernel version with git
Parent article: Finding a patch's kernel version with git
Except that your "obvious" is wrong.
Release 4 clearly can't contain commit 345, which occurred after release 4; but, thanks to branching, release 5 may also not contain commit 345. Consider the following timeline:
238 |TRUNK |release_4 tag
239 |TRUNK |Create release_4_maintenance branch
345 |release_4_maintenance|bugfix commit
525 |TRUNK |release_5 tag
It should be obvious that release 5 is not fixed, while some maintenance release of release 4 (say 4.1) is fixed. The apparent order in the commit ID has confused things, as while commit 345 happened before release 5 was tagged, it happened in a branch. I'm assuming here that thanks to human error, the developer forgot to ensure that the fix was present on TRUNK as well as the release_4_maintenance branch - this could happen if he's fixing it in a hurry because R4.1 is due out and this bug is important to a customer.
to post comments)