I'm studying the migration from our old Version Manager, Team Coherence
http://www.teamcoherence.com/, to Git.
One of the features we use in that system are file links:
Imagine a repo with this file structure:
- MyRepo1
- Folder1
- *FileA*
- FileB
- Folder2
- *FileA*
- FileC
From: Norike Abe nor...@gmail.com
I'm studying the migration from our old Version Manager, Team Coherence
http://www.teamcoherence.com/, to Git.
One of the features we use in that system are file links:
Imagine a repo with this file structure:
- MyRepo1
- Folder1
- *FileA*
-
Thanks for the comments, Dale!
What I don't see is why you'd want to have what is intended to be one
file implemented by two different files. That requires some sort of
machinery to ensure that the two instances of the file are always the
same, and introduces the constant possiblity of
