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 6bd107b.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>

Author: dscho

Git-cannot-create-a-file-or-directory-with-a-long-path.md

@@ -12,9 +12,6 @@ That being said, long paths support for C-based git commands can be enabled by s
 git config core.longpaths true
 ```
 
-> [!NOTE]
-> In addition to setting the git configuration the OS also needs to be configured to have longpaths enabled via the [Registry](https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry#registry-setting-to-enable-long-paths) or group policy.
-
 # Technical background
 
 The root cause of the technical limitation of 260 chars lies deeply within the Win32 API.