Comments on Comments (1)

(Generosity with questionable benefits) --- from /linux-3.17.1/net/ipv4/ping.c
* Pavel gave all rights to bugs to Vasiliy,  none of the bugs are Pavel's now. 

(History may not repeat, but it will misname things {at least in some versions}) -- /linux-2.4/include/(some versions of)/uaccess.h
* For historical reasons, these macros are grossly misnamed.

(We can't think of much to say here right now, but we're saying something anyway.) --- from Python-2.7.9/Modules/_ctypes/stgdict.c
* XXX blabla more

(What the world really needs is r/codegonewild) -- from git/patch-delta.c
*  /* sanity check */ if (data != top || size != 0) { error("delta replay has gone wild"); }

A logger for Corinthia

I managed to get the first cut written, and I got use the logmessage scribe.  Took 5 minutes to write the log message, woo!  Profit! :-))

Of course I found a couple of minor bugs in the logmessage scribe, mostly because I had to use GNU diff instead of git diff, but, I could not be happier.

Translation: if you're happy and you know it just say 'meow'!

Tree keeping made easy

If you want snazzy tree views for your project of your local drive files and the remote master repository that you can traverse with a browser, just modify this script and set up a cronjob to keep your trees updated.

How does it look?

Download the file itself, load it into your browser and have fun traversing the tree of the Corinthia GitHub repository. (blogger.com and google.drive won't let me paste the file without crippling the links, fair enough, it's 168 directories (and thus links) and usually people who do this kind of thing would probably be up to no good[1]).  If you just want to see it without working links, it's here.

I think it's nice to have a tree overview --- a picture is worth a 1000 words (as they say).

[1] sadly, saving the document also ninja-edits the original.  So, don't waste your time with pasting lots of links into Google Docs :(

Can't sleep?

Listen to Bertrand Russels's Introduction to Mathematical Philosophy.

You probably still won't fall asleep, but it's more productive and it beats counting sheep...

Adhoc profiling

./YourProgram | ts -i "%.s"

is a quick way of profiling your code.  Does of course not beat the real thing(tm), but for most purposes, this should give you a rough idea where your code spends it's time.

(You may need to install 'moreutils')

Some hacking music... because otherwise, there is just too much margin left in this blog post.