I’m never sure when my commits to Linux actually make it into an official release. Luckily, since releases are tagged, I can use “git tag --contains COMMIT” to find them. So, in a stunning display of inefficiency, here’s what I use to find my commits:
git log --author='Kees Cook' --pretty=oneline | \
while read commit name; do \
echo $(git tag --contains $commit | head -n1): "$name"; \
done
Which lets me know where my code is with respect to releases:
v2.6.33: x86, mm: Report state of NX protections during boot v2.6.33: sysctl: require CAP_SYS_RAWIO to set mmap_min_addr v2.6.32: proc: fix reported unit for RLIMIT_CPU v2.6.31: modules: sysctl to block module loading ...
© 2010, Kees Cook. This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 License.
You can also watch ohloh.net
http://www.ohloh.net/accounts/kees
It updates surprisingly quickly (at least for the linux kernel, new commits seem to show up within a day or two.)
Comment by SteveC — February 28, 2010 @ 1:39 pm
Or just
git log –author=’Kees Cook’ –pretty=oneline | git name-rev –stdin
Comment by Anders Kaseorg — March 1, 2010 @ 11:08 am
Cool; the name-rev output looks kind of like what it would change to if I swapped “head” for “tail” in my script.
Comment by kees — March 1, 2010 @ 2:00 pm