We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Here's the Weekly Digest for git-for-windows/git:
Last week 12 issues were created. Of these, 7 issues have been closed and 5 issues are still open.
💚 #2502 Git not ignoring case in filenames that are checked out from another commit, by eggonzal 💚 #2499 Git clean on a specific file does nothing, by joaomoreno 💚 #2498 Git-flow Extremely slow, by angelodiego 💚 #2495 Missing support for ISO 8601 date formats, by GisoBartels 💚 #2494 "git status" crashes in repositories with long file paths, by default0
❤️ #2504 Handle git add <file> where traverses an NTFS junction, by dscho ❤️ #2503 Shell window keeps opening on the "wrong" monitor, by binkleym ❤️ #2501 clink.pl: fix MSVC compile script to handle libcurl-d.lib, by jeffhostetler ❤️ #2500 Access denied for files under Git repositories after migration to Git 2.25.0.windows.1, by frederic-meyrou ❤️ #2497 Could you please package the 'rev' command with Git for Windows, by NBardelot ❤️ #2496 what?, by leonedithlozano ❤️ #2493 Invalid executable path error for git version :: mingit bundled with vsts-agent :: RAM Disk, by VenumadhavDuriseti
git add <file>
👍 #2494 "git status" crashes in repositories with long file paths, by default0 It received 👍 x1, 😄 x0, 🎉 x0 and ❤️ x0.
🔈 #2497 Could you please package the 'rev' command with Git for Windows, by NBardelot It received 17 comments.
Last week, 3 pull requests were created, updated or merged.
Last week, 3 pull requests were merged. 💜 #2504 Handle git add <file> where traverses an NTFS junction, by dscho 💜 #2501 clink.pl: fix MSVC compile script to handle libcurl-d.lib, by jeffhostetler 💜 #2489 Azure Pipeline: switch to the latest agent pools, by dscho
Last week there were 7 commits. 🛠️ Merge pull request #2504 from dscho/access-repo-via-junction Handle git add <file> where traverses an NTFS junction by dscho 🛠️ mingw: implement a platform-specific strbuf_realpath() There is a Win32 API function to resolve symbolic links, and we can use that instead of resolving them manually. Even better, this function also resolves NTFS junction points (which are somewhat similar to bind mounts). This fixes https://github.com/git-for-windows/git/issues/2481. Signed-off-by: Johannes Schindelin johannes.schindelin@gmx.de by dscho 🛠️ strbuf_realpath(): use platform-dependent API if available Some platforms (e.g. Windows) provide API functions to resolve paths much quicker. Let's offer a way to short-cut strbuf_realpath() on those platforms. Signed-off-by: Johannes Schindelin johannes.schindelin@gmx.de by dscho 🛠️ mingw: demonstrate a git add issue with NTFS junctions NTFS junctions are somewhat similar in spirit to Unix bind mounts: they point to a different directory and are resolved by the filesystem driver. As such, they appear to lstat() as if they are directories, not as if they are symbolic links. Any user can create junctions, while symbolic links can only be created by non-administrators in Developer Mode on Windows 10. Hence NTFS junctions are much more common "in the wild" than NTFS symbolic links. It was reported in https://github.com/git-for-windows/git/issues/2481 that adding files via an absolute path that traverses an NTFS junction: since 1e64d18 (mingw: do resolve symlinks in getcwd()), we resolve not only symbolic links but also NTFS junctions when determining the absolute path of the current directory. The same is not true for git add <file>, where symbolic links are resolved in <file>, but not NTFS junctions. Signed-off-by: Johannes Schindelin johannes.schindelin@gmx.de by dscho 🛠️ Merge pull request #2501 from jeffhostetler/clink-debug-curl clink.pl: fix MSVC compile script to handle libcurl-d.lib by dscho 🛠️ clink.pl: fix MSVC compile script to handle libcurl-d.lib Update clink.pl to link with either libcurl.lib or libcurl-d.lib depending on whether DEBUG=1 is set. Signed-off-by: Jeff Hostetler jeffhost@microsoft.com Signed-off-by: Johannes Schindelin johannes.schindelin@gmx.de by jeffhostetler 🛠️ [Merge pull request #2489 from dscho/azp-latest-pools Azure Pipeline: switch to the latest agent pools
strbuf_realpath()
git add
lstat()
getcwd()
<file>
See https://devblogs.microsoft.com/devops/removing-older-images-in-azure-pipelines-hosted-pools/ for details.](4b1502b) by dscho
Last week there were 2 contributors. 👤 dscho 👤 jeffhostetler
Last week there were 11 stagazers. ⭐ wakatsuki-moe ⭐ mahedi7up ⭐ Jorgeptz ⭐ thefireinyourflies ⭐ Jane-fine ⭐ janani-02 ⭐ mckabuza ⭐ epsilonmachine ⭐ xiaonoah ⭐ atomsyoung ⭐ abhijithvijayan You all are the stars! 🌟
Last week there were no releases.
That's all for last week, please 👀 Watch and ⭐ Star the repository git-for-windows/git to receive next weekly updates. 😃
You can also view all Weekly Digests by clicking here.
Your Weekly Digest bot. 📆
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Here's the Weekly Digest for git-for-windows/git:
ISSUES
Last week 12 issues were created.
Of these, 7 issues have been closed and 5 issues are still open.
OPEN ISSUES
💚 #2502 Git not ignoring case in filenames that are checked out from another commit, by eggonzal
💚 #2499 Git clean on a specific file does nothing, by joaomoreno
💚 #2498 Git-flow Extremely slow, by angelodiego
💚 #2495 Missing support for ISO 8601 date formats, by GisoBartels
💚 #2494 "git status" crashes in repositories with long file paths, by default0
CLOSED ISSUES
❤️ #2504 Handle
git add <file>
where traverses an NTFS junction, by dscho❤️ #2503 Shell window keeps opening on the "wrong" monitor, by binkleym
❤️ #2501 clink.pl: fix MSVC compile script to handle libcurl-d.lib, by jeffhostetler
❤️ #2500 Access denied for files under Git repositories after migration to Git 2.25.0.windows.1, by frederic-meyrou
❤️ #2497 Could you please package the 'rev' command with Git for Windows, by NBardelot
❤️ #2496 what?, by leonedithlozano
❤️ #2493 Invalid executable path error for git version :: mingit bundled with vsts-agent :: RAM Disk, by VenumadhavDuriseti
LIKED ISSUE
👍 #2494 "git status" crashes in repositories with long file paths, by default0
It received 👍 x1, 😄 x0, 🎉 x0 and ❤️ x0.
NOISY ISSUE
🔈 #2497 Could you please package the 'rev' command with Git for Windows, by NBardelot
It received 17 comments.
PULL REQUESTS
Last week, 3 pull requests were created, updated or merged.
MERGED PULL REQUEST
Last week, 3 pull requests were merged.
💜 #2504 Handle
git add <file>
where traverses an NTFS junction, by dscho💜 #2501 clink.pl: fix MSVC compile script to handle libcurl-d.lib, by jeffhostetler
💜 #2489 Azure Pipeline: switch to the latest agent pools, by dscho
COMMITS
Last week there were 7 commits.
🛠️ Merge pull request #2504 from dscho/access-repo-via-junction Handle
git add <file>
where traverses an NTFS junction by dscho🛠️ mingw: implement a platform-specific
strbuf_realpath()
There is a Win32 API function to resolve symbolic links, and we can use that instead of resolving them manually. Even better, this function also resolves NTFS junction points (which are somewhat similar to bind mounts). This fixes https://github.com/git-for-windows/git/issues/2481. Signed-off-by: Johannes Schindelin johannes.schindelin@gmx.de by dscho🛠️ strbuf_realpath(): use platform-dependent API if available Some platforms (e.g. Windows) provide API functions to resolve paths much quicker. Let's offer a way to short-cut
strbuf_realpath()
on those platforms. Signed-off-by: Johannes Schindelin johannes.schindelin@gmx.de by dscho🛠️ mingw: demonstrate a
git add
issue with NTFS junctions NTFS junctions are somewhat similar in spirit to Unix bind mounts: they point to a different directory and are resolved by the filesystem driver. As such, they appear tolstat()
as if they are directories, not as if they are symbolic links. Any user can create junctions, while symbolic links can only be created by non-administrators in Developer Mode on Windows 10. Hence NTFS junctions are much more common "in the wild" than NTFS symbolic links. It was reported in https://github.com/git-for-windows/git/issues/2481 that adding files via an absolute path that traverses an NTFS junction: since 1e64d18 (mingw: do resolve symlinks ingetcwd()
), we resolve not only symbolic links but also NTFS junctions when determining the absolute path of the current directory. The same is not true forgit add <file>
, where symbolic links are resolved in<file>
, but not NTFS junctions. Signed-off-by: Johannes Schindelin johannes.schindelin@gmx.de by dscho🛠️ Merge pull request #2501 from jeffhostetler/clink-debug-curl clink.pl: fix MSVC compile script to handle libcurl-d.lib by dscho
🛠️ clink.pl: fix MSVC compile script to handle libcurl-d.lib Update clink.pl to link with either libcurl.lib or libcurl-d.lib depending on whether DEBUG=1 is set. Signed-off-by: Jeff Hostetler jeffhost@microsoft.com Signed-off-by: Johannes Schindelin johannes.schindelin@gmx.de by jeffhostetler
🛠️ [Merge pull request #2489 from dscho/azp-latest-pools Azure Pipeline: switch to the latest agent pools
See https://devblogs.microsoft.com/devops/removing-older-images-in-azure-pipelines-hosted-pools/ for details.](4b1502b) by dscho
CONTRIBUTORS
Last week there were 2 contributors.
👤 dscho
👤 jeffhostetler
STARGAZERS
Last week there were 11 stagazers.
⭐ wakatsuki-moe
⭐ mahedi7up
⭐ Jorgeptz
⭐ thefireinyourflies
⭐ Jane-fine
⭐ janani-02
⭐ mckabuza
⭐ epsilonmachine
⭐ xiaonoah
⭐ atomsyoung
⭐ abhijithvijayan
You all are the stars! 🌟
RELEASES
Last week there were no releases.
That's all for last week, please 👀 Watch and ⭐ Star the repository git-for-windows/git to receive next weekly updates. 😃
You can also view all Weekly Digests by clicking here.
The text was updated successfully, but these errors were encountered: