The other day I was chasing ghosts for half a Day: I had a git repo in which all Symlinks
where replaced with a one line file containing the link target. WTF?

Only after a while it dawned on me that the only difference was that I had cloned the repo with Egit(Eclipse).
Egit is implemented in Java. Java has no symlink support (up to Java 7). OK. But why no symlinks with native git?
Because it was told so. The core section in the .git/config file looked like this:

[core]
    repositoryformatversion = 0
    filemode = true
    bare = false
    symlinks = false
    logallrefupdates = true

Notice 'symlinks = false'. Delete it and you are good for native git. You may have to reset/re-checkout.

But what about Eclipse/Egit?

There is a long running Bug in Eclipse Bugzilla: #354367
Wich says it is done for JGit the underlying library for egit. When you follow the referenced Bugs there it is also
said that this is done for Java 7/Egit. I am running Eclipse with Java 7 so where is it?

Hidden.

There is an extra Installable in the egit software repo in eclipse: Optional Java 7 libraries.

In Eclipse go to Help → Install New software.. → In the Work With: Dropdown select
egit - http://download.eclipse.org/egit/updates open the JGit Tree and install:
Java Implementation of Git - optional Java 7 libraries

Restart Eclipse. Clone a repo and there you are: Symlinks.

Marijn Haverbeke has written an (opinionated) book on programing with
JavaScript:

http://eloquentjavascript.net/

.. Eloquent JavaScript is a digital book providing a comprehensive
introduction (tutorial) to the JavaScript programming language. Apart
from a bookful of text, it contains plenty of example programs, and an
environment to try them out and ...

Apparently the Java runtime has options that can execute commands when a
JVM crashes.

http://prefetch.net/blog/index.php/2008/01/29/getting-alerts-when-java-processes-crash/

Matty writes how to have a look at what the Java Garbage Collector is
doing:

http://prefetch.net/blog/index.php/2008/01/16/monitoring-garbage-collection-with-jstat/

Normally you would use the export functionality of svn:

svn export path/to/workingcopy path/to/export

But sometimes Murphy is harsh on you:

svn: This client is too old to work with working copy 'working_copy;
please get a newer Subversion client

A simple method is to remove all .svn ...