"Matt Seitz (matseitz)" <matseitz@xxxxxxxxx> wrote: > Where does the git user documentation discuss how git handles symbolic > links? About the only mention I can find appears to be in git-config where it talks a little bit about the core.symlinks configuration option. But in general Git treats symlinks as though they were plain text files. The content of the "file" is the target of the symlink. Use `git-add link` to stage the symlink for the next commit (just like a file), `git-mv` to rename a symlink (just like a file), etc. Editing a symlink to point to a new target is just a matter of using the OS' tools (e.g. `ln -sf newdst link`). So long as core.symlinks isn't set or is set to true Git will recreate the symlink upon checkout of the revision, just like it recreates plain text files. -- Shawn. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
