For work, I have a virtual machine serving one little purpose: To run Microsoft Internet Explorer 6, for the rare instances when I have to test a website with it. To make that a little more convenient and a little less painful, I just created a “desktop shortcut” for it, and look what it showed up as:

Haha, “Shortcut to Internet” — this is classic.

Just a reminder, because I always forget it: When you use git-svn on an svn repository and your code base contains empty directories (say, for temporary files, or log files), they will be ignored by git unless they contain at least one file.

Paradox? Maybe. There’s a good reason however: git ignores empty directories because it tracks (file) content, not a bunch of directories some of which happen to contain a file (the concept of tracking files might be the only thing git has remotely in common with good ol’ CVS — though git also does not deeply care about file names, only content).

The “common” way to handle this is by adding a .gitignore file to the repository. This won’t harm svn-only clients, but it’ll make git-svn clients pick up the (almost) empty directory properly.

This is what you need to do.

mkdir empty_dir
echo '*' > empty_dir/.gitignore
echo '!.gitignore' >> empty_dir/.gitignore
git add empty_dir
git commit -m 'adding empty directory' empty_dir

The .gitignore file tells git what file names not to track inside the directory in question. The asterisk means, ignore all files, but the second line makes sure the .gitignore file itself is recognized and added to the repository.

photo credit: flodIn a very well written article that was published in Sunday’s New York Times, Miguel Helft explains the post-”browser wars” web, and how Mozilla’s mission fits into this increasingly complex setup.

As indicated by the title — “For Mozilla and Google, Group Hugs are Getting Tricky”, the author puts some emphasis onto the Google/Mozilla relationship, which among the community tends to be a big point of interest. Quote:

“In many ways, Google and Mozilla are fighting the same battle, albeit not with the same objectives. They both contend that the Web should be open and based on common standards — Mozilla because it is its mission, Google because it is good for its business.”

Highly recommended reading, even for non-geeks, who are interested in Mozilla and the Web as a whole.

Link