We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Yet another deep link found
I found another deep link
Redirect #experimental-busybox-based-mingit
FAQ: special-case the "should I upgrade" question Signed-off-by: Johannes Schindelin <[email protected]>
Redirect "0 Index" and "_Footer" correctly In the previous commit, I redirected all wiki pages to their new location. This was done in an automated fashion and therefore did not exempt the two pages that were dropped during the migration in https://github.com/git-for-windows/git-for-windows.github.io/pull/59/commits/c45fb638b3b2a These two pages were dropped because they played roles that are now played by other pages, so let's adjust the original wiki pages to point to those other pages instead. Signed-off-by: Johannes Schindelin <[email protected]>
Replace all page contents with links to the new location This trick was performed via: git ls-files \*.md | while read f do pr_url=https://github.com/git-for-windows/git-for-windows.github.io/pull/59 url=https://gitforwindows.org/${f%.md} echo "This wiki page [has been migrated]($pr_url) to a new location: [$url]($url)" >"$f" done There are two pages where this does not make sense, `0.-Index` and `_Footer`, which will be handled in the next commit. Signed-off-by: Johannes Schindelin <[email protected]>
Stop referring to the Google Group; It was shut down. Signed-off-by: Johannes Schindelin <[email protected]>
Revert "Updated Git cannot create a file or directory with a long path (markdown)" Contrary to the claim made in this commit, the registry setting is not required for Git for Windows' long paths support to work. This reverts commit 6bd107b1242880f1a49d3464e969de4e15de9c7b. Signed-off-by: Johannes Schindelin <[email protected]>
Revert "Updated Git cannot create a file or directory with a long path (markdown)" This commit claimed that `cmd.exe` can work with long paths, but that is only the case when editing the registry, in ways that most users will never learn about. So let's avoid claiming that it works. This reverts commit 5a5d8d0ab281004b0f806a3d7574ae6f3488c50f. Signed-off-by: Johannes Schindelin <[email protected]>
Updated Git cannot create a file or directory with a long path (markdown)
Improve markup of the initial notices
Do suggest to upgrade to at least 2.47.1(2)
Clarify that there is limited support for aliases and hooks
Mention the latest security release
Dev Drives are probably the most commonly used ReFS drives, so much so that many users do not even realize it's ReFS
Clarify that ReFS supports symbolic links
Updated FAQ (markdown)
add a link to Victoria Dye's excellent blog post
Update the note clarifying that we're following Cygwin in dropping support for outdated Windows versions.
Note that 32-bit versions do not enjoy full support anymore, and Windows 7 & 8 support has been dropped, too.
Mention the newest security bug-fix release
Revert 6ffc9b132e445d74bfeb9c286eacb2db1d94e81c...325fc9b01f16aac3fd32257f72be8bbc7c222723
Destroyed FAQ (markdown)
Bring the "Why, How, What" of the updates in continuity
Whoops, forgot to adjust some parts the the new lay of the land.
Adjust the documentation to how things are done now using the GitForWindowsHelper GitHub App
Revert ca955c8fd2837496fedc31d557ec0f983be99034...0298fb627f6054db3fd20fb7a4af1f9d4328e123 on _Footer
Updated _Footer (markdown)