To build these kernels, I use a script called mainline-build-one, which is in the kteam-tools repository[0].
The script comes up with the name of the .deb by using the date and the git command 'git describe SHA1'. So in the case of the last commit tested:
git describe fdd050b5b3c96813ae6756ed68157d32ba31b9f2 v4.12-rc5-66-gfdd050b
If the script used '--contains' with git describe, it would report the actual kernel version that contains that commit, for example:
git describe --contains fdd050b5b3c96813ae6756ed68157d32ba31b9f2 v4.13-rc1~70^2~67^2~42
[0] git://git.launchpad.net/~canonical-kernel/+git/kteam-tools
To build these kernels, I use a script called mainline-build-one, which is in the kteam-tools repository[0].
The script comes up with the name of the .deb by using the date and the git command 'git describe SHA1'. So in the case of the last commit tested:
git describe fdd050b5b3c9681 3ae6756ed68157d 32ba31b9f2 66-gfdd050b
v4.12-rc5-
If the script used '--contains' with git describe, it would report the actual kernel version that contains that commit, for example:
git describe --contains fdd050b5b3c9681 3ae6756ed68157d 32ba31b9f2 70^2~67^ 2~42
v4.13-rc1~
[0] git://git. launchpad. net/~canonical- kernel/ +git/kteam- tools