codeblog code is freedom — patching my itch

2/28/2010

egosurfing with git

Filed under: Blogging,Debian,Ubuntu,Ubuntu-Server — kees @ 12:19 pm

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 3.0 License.
Creative Commons License

3 Comments »

  1. 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 — 2/28/2010 @ 1:39 pm

  2. Or just
    git log –author=’Kees Cook’ –pretty=oneline | git name-rev –stdin

    Comment by Anders Kaseorg — 3/1/2010 @ 11:08 am

  3. 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 — 3/1/2010 @ 2:00 pm

Leave a Reply

Your email address will not be published. Required fields are marked *

Powered by WordPress