-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
git config overwrites symbolic links #958
Comments
This is really old by now. There have been 2.9.3, 2.9.3(2), 2.10.0, 2.10.1 and 2.10.2 in the meantime. Nevertheless, I tested it and figured out what goes wrong: our But we should read symbolic links whenever we encounter one, regardless of our ability to create symbolic links. |
When encountering a symbolic link, Git [now always tries to read it](git-for-windows/git#958), not only when `core.symlinks = true`. Signed-off-by: Johannes Schindelin <[email protected]>
Thank you so much for the quick fix! |
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes #958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes #958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes #958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes git-for-windows#958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes #958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes git-for-windows#958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes #958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes #958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes #958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes #958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes #958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes #958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes #958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes #958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes #958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes #958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes #958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes #958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes #958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes #958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes #958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes #958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes #958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes #958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes git-for-windows#958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes git-for-windows#958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes git-for-windows#958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes #958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes git-for-windows#958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes #958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes #958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes #958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes git-for-windows#958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes git-for-windows#958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes #958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes git-for-windows#958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes #958 Signed-off-by: Johannes Schindelin <[email protected]>
Regardless whether we think we are able to create symbolic links, we should always read them. This fixes #958 Signed-off-by: Johannes Schindelin <[email protected]>
Setup
defaults?
to the issue you're seeing?
n/a
Details
Cmd ("As Administrator")
Minimal, Complete, and Verifiable example
this will help us understand the issue.
The last
dir .git\config
command shows that the file is a SYMLINK:The last
dir .git\config
command shows that the SYMLINK has been replaced by a file:URL to that repository to help us with testing?
The problem is not specific to a particular repository. Even though the example seems trivial, the issue is actually affecting "real-world" examples, specifically people using the https://code.google.com/p/git-repo/ tool to handle multiple repository. The git-repo tool create many symblic links in ".git" directories, and it does not expect these symbolic links to be replaced by regular files.
Note that git for cygwin preserves symlinks with a similar set of commands.
The text was updated successfully, but these errors were encountered: