Heads up: I'm switching my comments to Disqus. I had several people complaining about the current HaloScan-based system. Expect minor disturbances in the force. Update: we are now Disqus-powered. They still don't have an importer for old comments, so for a while, old comments are orphaned. Hope they fix that soon.
I missed the release of the new 1.5.0 version of Subversion. Its funny, actually. This was somewhere around June (the blog post lacks a proper date), and I didn't see it mentioned on any of the blogs I follow. Anyway, its out and I was expecting it to see the new merge tracking stuff. One of my gripes with Subversion is that yes, branching is cheap, but the merge part is awful hard to do and puts much of the load into your lap.
I've tried at least twice now to move from ecto to MarsEdit, but I was having some problems moving my ecto setup from 10.4.x to 10.5.4, so I decided to give it another try. This time it seems to be working much better. Local Markdown works, and I could define my usual shortcuts easily with the markup editor. I've still haven't found a way to import all my posts (I want to have the full history locally), so I'll have the check the manual for that one.
Really, its disgusting how low you can get. Here we can see Nik Cubrilovic ranting about how close the iPhone is and all the DRM plague that it brings to our world. Cool, thats nice, and certainly a valid point of view. It's certainly better written than the usual diatribe we get from the Portuguese open source evangelists. But take a moment to search the TechCrunchIT site for openmoko. You can just click the last word.
I removed all traces of the multiple feeds this site had to just one: http://www.simplicidade.org/notes/42.xml. I've also added redirects on all of the old feeds to that one, so unless your feed reader cannot read RSS 2.0 it should all work out. Feed Validator tells me that I have three things to fix at the moment. I'll probably fix two of them (done). The other is content related, and I don't know of a easy fix.
I'll delete this post in a bit, but I need to test something, sorry bout that :) Second part (extended) goes here.
The silence around here is caused by a 100% increase on the house population. Our dog, Ginger, was pregnant and gave birth to 6 new puppies (pictures as soon as I get some power into my phone). The problem was with the first puppy. It was too big (the father dog was bigger than her, so this puppies are big..) and she was couldn't deliver the puppies on her own. So she had to do a C-section.
I'm looking for a desktop Mac. I'm pretty unhappy with the current Apple offering. We have the high-end Mac Pro, starting at 2.499â¬ (but you can configure a single CPU version for 2.049â¬, and at the low end, the Mac mini, starting at 499â¬. In the middle we have the iMac's but those have a built-in screen, and I already have dual 20" Wide displays that I would like to reuse.
Dear Lazyweb, this is something that I searched for quite some time and could not find yet, maybe a helpful soul knows. In a bourne shell script, how can I find the full path of the script being executed? Thanks in advance. Update: the following command, sent by Celso Pinto, passes all my tests. SCRIPTDIR="cd $(dirname $0);pwd For the record, I used two scripts to test this. First, the script_dir.sh script:
In case you use the script from the last post, be advised that the current master branch of git.git no longer installs all those git-* on your PATH. The current git/bin/ contents are: [email protected]:melo $ ls -l /usr/local/git/bin total 14664 -rwxr-xr-x 89 root wheel 2826820 Jul 4 10:05 git -rwxr-xr-x 1 root wheel 573476 Jul 4 10:05 git-receive-pack -rwxr-xr-x 1 root wheel 2826820 Jul 4 10:05 git-upload-archive -rwxr-xr-x 1 root wheel 994596 Jul 4 10:05 git-upload-pack -rwxr-xr-x 1 root wheel 273636 Jul 4 10:05 gitk I'm using version v1.