symlinks

Hello,

I have a project that makes heavy use of symlinks in the source tree.
I added it to git, then cloned the repository, and all symlinks were
converted to plain files. What am I missing to preserve symlinks ?

Yakov

On Sun, 7 May 2006, Yakov Lerner wrote:

I have a project that makes heavy use of symlinks in the source tree.
I added it to git, then cloned the repository, and all symlinks were
converted to plain files. What am I missing to preserve symlinks ?

You're not missing anything, it sounds like a bug. What did you use to 
clone, and what version? It definitely doesn't happen for me:

	mkdir symlink
	cd symlink/
	git-init-db 
	ln -s unknown new-link
	ls -l
	git add new-link 
	git commit

	cd 
	git clone symlink symlink2
	cd symlink2/
	ls -l

shows that the symlink was preserved.

But maybe there's a bug in some older version, or in some other clone 
protocol...

		Linus

On 5/7/06, Linus Torvalds [off-list ref] wrote:

On Sun, 7 May 2006, Yakov Lerner wrote:

quoted

I have a project that makes heavy use of symlinks in the source tree.
I added it to git, then cloned the repository, and all symlinks were
converted to plain files. What am I missing to preserve symlinks ?

You're not missing anything, it sounds like a bug. What did you use to
clone, and what version? It definitely doesn't happen for me:

       mkdir symlink
       cd symlink/
       git-init-db
       ln -s unknown new-link
       ls -l
       git add new-link
       git commit

       cd
       git clone symlink symlink2
       cd symlink2/
       ls -l

shows that the symlink was preserved.

Yes, I see now it's not git problem. I suspect
I just incorrectly copied the files into git-init-db directory,
something like 'cp -r' instead of 'cp -a' or tar/cpio. Sorry I'm
new to git.

Thanks
Yakov