That sounds a bit fishy. I'm guessing someone actually checked in a symlink
file into SVN, and that's the one that appeared in your local repo.
Check it with
git cat-file -p HEAD:mylibs
This will print the contents of the file as it is checked into the
repository. It should print something like
../mylibs%
You can also do a git log on the symlink file to see who checked it in
when, etc.
If git complains that it is not a valid object name, then it isn't checked
in, and only exists on your disk. That means you either created the symlink
unknowingly (or maybe your pairing partner, etc), or git-svn has some
hidden feature of doing this, but I can't find any notion of such a feature
when searching around.
Now, git-svn does scan for svnprops, and can do some handling of some of
these (svn:ignore for example). I doubt however that it did something
intelligent with the svn:externals property here. You could show us what
the externals are actually set to be though. git svn propget svn:externals
or something like that.
--
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
