Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • In the end, I chose this approach to create a symlink-out folder and create the symbolic links to where the original file used to be. The other approach didn't work even after I changed .git/config setting core.symlinks = true. Only the symbolic link file was saved to the repo and not the data. Also had problems with folder timestamps on the symbolic link so git bash never saw when a file changed within the folder. Commented Apr 20, 2018 at 4:49
  • @Eggs what you might have been seeing, I guess, is that the link was within the repo, and so git saved it, simples. The problem though is that the target was outside of the repo, and git does not follow the link to the target data. On linux you have a type of link that would work for this, it's basically let's you have two paths to the same data stored on disk; I've a feeling newish windows can do this now. Either way though, I still don't think it's going to do what people want. Commented Apr 20, 2018 at 8:36
  • @thecoshman This is not a solution, but a workaround. However, sometimes this is not an option. I have a repository with git-annex an all its architecture works because of symbolic links. Commented Aug 3, 2018 at 18:32
  • What is "MG"? Do you mean Mercurial (hg)? Commented Jun 13, 2022 at 22:28