git/list[1] front-page[2] threads[3] people[4] search[5] about
 

symlink issue in 2.49.0.windows.1

From
CCConti, Chris <chris.conti@pega.com>
Date
May 16, 2025, 21:49 UTC
Message-ID
<BN6PR13MB3091D0E52DBC0D6F60B6C95E9493A@BN6PR13MB3091.namprd13.prod.outlook.com>

What did you do before the bug happened? (Steps to reproduce your issue) I have an alias that enables core.symlinks from the command line:

relevant lines from my system gitconfig: core.symlinks=false

relevant lines from my user .gitconfig: difftool.bc4diredit.cmd="c:/Program Files/Beyond Compare 4/BCompare.exe" -lro -expandall -solo "$LOCAL" "$REMOTE" alias.diffdirsym=-c core.symlinks=true difftool --dir-diff --tool=bc4diredit --no-prompt

execution (in a repo with a changed file) git diffdirsym

execution environment elevated powershell 5.1 shell

What did you expect to happen? (Expected behavior)
for the command to work
What happened instead? (Actual behavior)

received a "Function not implemented" error: error: could not symlink '<redacted physical path to changed file>' to 'C:\Users\contc\AppData\Local\Temp/git-difftool.a49272/right/<redacted relative path to copy of changed file>': Function not implemented

What's different between what you expected and what actually happened?
Anything else you want to add:
verified the alias works in 2.48.1.windows.1

Please review the rest of the bug report below. You can delete any lines you don't wish to share.

[System Info]
git version:
git version 2.49.0.windows.1
cpu: x86_64
built from commit: cca1f38702730b35f52c29efd62864b85e85ddcc
sizeof-long: 4
sizeof-size_t: 8
shell-path: D:/git-sdk-64-build-installers/usr/bin/sh
feature: fsmonitor--daemon
libcurl: 8.12.1
OpenSSL: OpenSSL 3.2.4 11 Feb 2025
zlib: 1.3.1
uname: Windows 10.0 19045
compiler info: gnuc: 14.2
libc info: no libc information available
$SHELL (typically, interactive shell): <unset>
[Enabled Hooks]
Chris Conti
Email: chris.conti@pega.com | pega.com
Next: Johannes Schindelin
Message 1 of 2 in “symlink issue in 2.49.0.windows.1”
  1. Conti, ChrisMay 16, 2025
  2. Johannes SchindelinJul 17, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.