Currently when we build release [candidate] releases, the kernel could be reused from a previous build. This has no operational impact but it does mean that package versioning looks messy. For example, from the 2.1.1 release:

kernel-2.6.32-220.el6_lustre.g4554b65.x86_64.rpm

The "g4554b65" in the version is because for the release a kernel was reused from a previous non-RC build which is what caused the git hash to be included in the version. Had a new kernel build for the RC release been forced it would not have had the git hash in it because it would have been built from a tagged release.