3 Aug 2007 zeenix   » (Journeyer)

The new Spock:

Guess who is going to play the role of Spock in the coming Star Trek movie? No! wait! don't waste your precious time and brain resources because you simply can't guess this one. The person chosen for this role is none other than Zachary Quinto. Who is that? he is the 'Sylar' in Heroes. :) We had some fun over this fact after i found it out last night:


<zeenix> guess who has been selected for the role of
spock in the coming star trek?
<jumpula> matt damon?
<zeenix> no no
<zeenix> that was for kirk
<zeenix> it's it's it's
<zeenix> 'Sylar' :)
<jumpula> noeees...
<zeenix> i am having trouble imaging him saying 'Live
long and prosper' :)
<jumpula> i'll bet he eats kirk's brains first chance
he gets
<jumpula> and kirk is matt damon?
<jumpula> this is bad :D
<zeenix> :D
<zeenix> and he'll say 'logic dictates that i eat your
brain' :)
<jumpula> :)
<jumpula> the needs of the one outweigh the needs of
the many
<jumpula> wonder if he get's the kirk's luck with the
ladies from the brain
<zeenix> lol

GUPnP tools

In my last communication with jorn regarding the universal control-point, he suggested to keep this in a separate package and it made sense since there shall be two binaries of the control-point provided, a console-based and gtk+ one and I am thinking of adding at least one more tool: a simple light-bulb, a free replacement for Intel's light-bulb, which would be a very nice and simple example of a gupnp-based control-points. All this combined with the fact that a separate package would allow me to use git all the way. :P There were two problems however:

  1. How do you move a particular directory from one git repo/project to another with all the history intact? I asked daniels if there is way to do that and he advised me to try out git-format-patch and git-am and that is what i did. After playing with git for a while last night, I was able to achieve my goal before 2am. :) Turns out that it's very simple if you know what to do:

    git-format-patch -o /tmp --binary <commit1> [commit2]

    where 'commit1' is the id of the last commit before the first commit to that dir and 'commit2' is the last one which you can skip if all commits after 'commit1' are to the same dir. You can find the commit ids to use through 'git-log' command. You'll get a bunch of patches in your cwd after this step. Skim through those patches and remove/edit them if necessary. Then go to the directory of the repo/project where you want to move your stuff to and:

    git-am /tmp/*.patch

    And you are done. :) Make sure there are no other patches in /tmp.

  2. I'll need to setup my git repo on a machine visible to everyone, which is static.fi for me. The admin told me that he is going to set it up but after he is finished with assembly (which is next week). The problem is that I (and some other git users either) don't know how to clone a repo. from my machine (which is always behind a NAT) to a remote machine. I heard it's only possible if there is a git daemon running on the other machine and I don't know if that admin friend of mine would allow that.

Latest blog entries     Older blog entries

New Advogato Features

New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.

Keep up with the latest Advogato features by reading the Advogato status blog.

If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!