Replace all links to the wiki with relative links

Since we no longer want to let random people edit the wiki, let's not
point readers there, either. The idea is to replace the wiki pages with
links to the corresponding pages on Git for Windows' home page, anyway,
therefore we can point readers there directly.

Signed-off-by: Johannes Schindelin <[email protected]>

Author: dscho

content/_index.md

@@ -56,7 +56,7 @@ Simply right-click on a folder in Windows Explorer to access the BASH or GUI.
 <div class="vcentercontainer detailstext">
 <div>
 
-As an open source project, Git for Windows benefits greatly from both the volunteer work of helpful developers and [good bug reports](https://github.com/git-for-windows/git/wiki/Issue-reporting-guidelines) made by Git for Windows' users.
+As an open source project, Git for Windows benefits greatly from both the volunteer work of helpful developers and [good bug reports](./issue-reporting-guidelines.html) made by Git for Windows' users.
 
 ### Governance Model
 
@@ -72,7 +72,7 @@ If you've noticed a bug or simply have an idea that you'd like to see become rea
 
 The _Git for Windows SDK_ is a build environment that includes all the tools necessary for developers who want to contribute by writing code for Git for Windows.
 
-Please look at the [technical overview](https://github.com/git-for-windows/git/wiki/Technical-overview) of the Git for Windows packaging and how to include your changes in your own custom installer.
+Please look at the [technical overview](./technical-overview.html) of the Git for Windows packaging and how to include your changes in your own custom installer.
 
 <a name="download-sdk" /><a class="button" href="https://github.com/git-for-windows/build-extra/releases/latest" target="_blank">Download <span class="gittext">Git for Windows SDK</span></a>
 

content/building-git.md

@@ -33,7 +33,7 @@ Once the SDK built Git, it is *very* easy to build another revision of Git, such
  1. if you want to test a Pull Request, call `git fetch origin refs/pull/<id>/head`, where `<id>` is the number of the Pull Request (e.g. if you want to test Pull Request #606, you would call `git fetch origin refs/pull/606/head`),
  2. if you want to test a custom branch, call `git fetch <url> <branch>` instead, where `<url>` is the URL of the repository and `<branch>` is the name of the branch to test (e.g. if you wanted to test @dscho's `cool-new-feature` branch, you would call `git fetch https://github.com/dscho/git cool-new-feature`),
 4. check out the revision that was just fetched: `git checkout FETCH_HEAD`,
-5. continue as [above](https://github.com/git-for-windows/git/wiki/Building-Git#build-git) either by `make install` or `make test`.
+5. continue as [above](./building-git.html#build-git) either by `make install` or `make test`.
 
 ## Updating to the newest Git for Windows version
 
@@ -55,7 +55,7 @@ cd /usr/src/git/t
 ## See also Regression Testing
 
 Single tests, block of tests, or the whole test suite can be run, as detailed in
-[Running Git's regression-tests](https://github.com/git-for-windows/git/wiki/Running-Git's-regression-tests)
+[Running Git's regression-tests](./running-gits-regression-tests.html)
 
 
 ---

content/building-new-package-versions.md

@@ -3,7 +3,7 @@ title: "Building new package versions"
 aliases:
   - "Building-new-package-versions"
 ---
-As described in [Package management](Package-management), Git for Windows' SDK is a close derivative of the [MSYS2](https://msys2.github.io/) system, and as such, its components are built using `makepkg` and `makepkg-mingw` (borrowed from Arch Linux' [`pacman`](https://wiki.archlinux.org/index.php/Pacman)).
+As described in [Package management](./package-management.html), Git for Windows' SDK is a close derivative of the [MSYS2](https://msys2.github.io/) system, and as such, its components are built using `makepkg` and `makepkg-mingw` (borrowed from Arch Linux' [`pacman`](https://wiki.archlinux.org/index.php/Pacman)).
 
 Most of those packages are actually built by the MSYS2 project and consumed by Git for Windows. However, a couple of components (including cURL and OpenSSH) _are_ built by Git for Windows, e.g. to be able to react faster to newly-available versions, or to allow for modifications specific to Git for Windows.
 
@@ -42,4 +42,4 @@ The strategy that worked best for the Git for Windows maintainer goes like this:
 9. test (`cd ../.. && sdk build`)
 10. commit, push (and open a PR unless pushing directly to `main`)
 
-Caveat: this strategy needs manual adjustments if the archive in question contains files with DOS line endings (I am looking at you, [Perl](https://github.com/git-for-windows/git/wiki/Upgrading-the-%60perl%60-component-to-a-new-version) _shakes fist_): `import-tars.perl` will happily import those verbatim, but the `bsdtar` used by `makepkg` to unpack the archive will convert them to Unix line endings, and if the patches expect DOS line endings, they won't apply.
+Caveat: this strategy needs manual adjustments if the archive in question contains files with DOS line endings (I am looking at you, [Perl](./upgrading-the-perl-component-to-a-new-version.html) _shakes fist_): `import-tars.perl` will happily import those verbatim, but the `bsdtar` used by `makepkg` to unpack the archive will convert them to Unix line endings, and if the patches expect DOS line endings, they won't apply.

content/compiling-git-with-visual-studio.md

@@ -12,7 +12,7 @@ Please note: this page describes how to compile Git's source code in Visual Stud
 > [!WARNING]  
 > The `vs/main` branch and `git.sln` is deprecated. The current approach is to open the `git` folder in VS directly, refer to the [README of the `vs/main` branch](https://github.com/git-for-windows/git/tree/vs/main).
 
-Git's source code (and hence also Git for Windows' source code) is [usually built using GNU C and GNU Make in a Git for Windows SDK](https://github.com/git-for-windows/git/wiki/Building-Git).
+Git's source code (and hence also Git for Windows' source code) is [usually built using GNU C and GNU Make in a Git for Windows SDK](./building-git.html).
 
 However, as of Git for Windows v2.11.0, a much more convenient way is available: by cloning https://github.com/git-for-windows/git and checking out the `vs/main` branch, you will automatically have project definitions ready to go with Visual Studio.
 
@@ -47,4 +47,4 @@ prove --timer --jobs 15 ./t[0-9]*.sh
 
 ## Browsing the code
 
-You can also use the Sourcetrail code browser (now open source) in conjunction with Visual Studio, see [Sourcetrail code viewer](https://github.com/git-for-windows/git/wiki/Sourcetrail-code-viewer-and-linkage-to-Visual-Studio,-for-Git) page.
+You can also use the Sourcetrail code browser (now open source) in conjunction with Visual Studio, see [Sourcetrail code viewer](./sourcetrail-code-viewer-and-linkage-to-visual-studio-for-git.html) page.

content/contact.md

@@ -9,7 +9,7 @@ Please state the nature of your medical emergency.
 
 ## I found a bug!
 
-Please follow [our guide lines](https://github.com/git-for-windows/git/wiki/Issue-reporting-guidelines) on reporting bugs.
+Please follow [our guide lines](./issue-reporting-guidelines.html) on reporting bugs.
 
 ## I have a question!
 

content/diagnosing-performance-issues.md

@@ -13,7 +13,7 @@ If the problem lies with a specific Git command, the most straight-forward way t
 
 The canonical profiling tool in GCC's tool set is [`gprof`](https://sourceware.org/binutils/docs/gprof/). However, the MINGW version of the GCC tools offered by MSYS2 has been known to produce empty output on occasion.
 
-An more convenient alternative is to use [Visual Studio's Performance Profiler](https://github.com/git-for-windows/git/wiki/Performance-profiling-with-Visual-Studio) (which is available in the free-of-cost Community version) which offers a powerful graphical user interface.
+An more convenient alternative is to use [Visual Studio's Performance Profiler](./performance-profiling-with-visual-studio.html) (which is available in the free-of-cost Community version) which offers a powerful graphical user interface.
 
 ## Trace executions in the Bash startup
 

content/faq.md

@@ -48,15 +48,15 @@ This depends on how you installed *Git for Windows*. The bundle installation req
 
 *Git for Windows* comes with a tool to check for updates and offer to install them. Whether or not you enabled auto-updates during installation, you can manually run `git update-git-for-windows`. (For help, run `git update-git-for-windows -h`.)
 
-For advanced users working with the *Git for Windows* SDK `pacman` is available as a package manager. See [Package management](Package-management)
+For advanced users working with the *Git for Windows* SDK `pacman` is available as a package manager. See [Package management](./package-management.html)
 
 ## How do I check the release hash and release notes
 
 For hashes see https://github.com/git-for-windows/git/releases
 
 For (G4W) release notes see the [build-extra repo](https://github.com/git-for-windows/build-extra/blob/HEAD/ReleaseNotes.md), or the top level of your installation (e.g. [C:\Program Files\Git\ReleaseNotes.html](https://www.example.com/Program%20Files/Git/ReleaseNotes.html) - via manual browsing).
 
-For extracting 7z/zip archives see [page](https://github.com/git-for-windows/git/wiki/Zip-Archives---extracting-the-released-archives).
+For extracting 7z/zip archives see [page](./zip-archives-extracting-the-released-archives.html).
 
 ## Are there 'Nightly' builds of the latest and greatest
 
@@ -77,7 +77,7 @@ Finally, Git for Windows is sometimes released in "out-of-band" versions, when c
 
 ## What is the relationship between *Git for Windows* and *msysGit*?
 
-*Git for Windows* used to be developed using the development environment called "msysGit", but roughly coinciding with Git 2.1, msysGit was superseded by a new development environment: the [Git for Windows SDK](https://github.com/git-for-windows/build-extra/releases). See [here](https://github.com/git-for-windows/git/wiki/Updating-your-SDK) to get a copy.
+*Git for Windows* used to be developed using the development environment called "msysGit", but roughly coinciding with Git 2.1, msysGit was superseded by a new development environment: the [Git for Windows SDK](https://github.com/git-for-windows/build-extra/releases). See [here](./updating-your-sdk.html) to get a copy.
 
 ## Some native console programs don't work when run from Git Bash. How to fix it?
 
@@ -93,7 +93,7 @@ There are several methods for working around these problems:
  * Install and use [ConEmu](https://conemu.github.io/).
 
 ## I get errors trying to check out files with long path names.
-Windows file paths are by default limited to 260 characters. Some repositories may have committed files which contain paths longer than the limit. By default, *Git for Windows* does not support long paths, and will print errors when trying to perform any operation on a long file name. Set the configuration property `core.longpaths` to true to allow certain Git operations to properly handle these files. See [this wiki page](https://github.com/git-for-windows/git/wiki/Git-cannot-create-a-file-or-directory-with-a-long-path) for more information.
+Windows file paths are by default limited to 260 characters. Some repositories may have committed files which contain paths longer than the limit. By default, *Git for Windows* does not support long paths, and will print errors when trying to perform any operation on a long file name. Set the configuration property `core.longpaths` to true to allow certain Git operations to properly handle these files. See [this wiki page](./git-cannot-create-a-file-or-directory-with-a-long-path.html) for more information.
 
 ## The installed files are duplicated and look massive - Why?
 All the apparent copies are simply hard links - see Issue  1997 [Use symbolic links for libexec](https://github.com/git-for-windows/git/issues/1997) for more details.

content/git-wrapper.md

@@ -25,7 +25,7 @@ The actual programs, e.g. `bash.exe` or `git.exe`, live in `<Git>\usr\bin` and `
 
 - **`MSYSTEM`**
 
-  To accommodate Git's expectations where it assumes e.g. a Unix shell to be present on the `PATH`, Git for Windows ships with a subset of [MSYS2](https://msys2.github.io/) (find out about more historical context [here](https://github.com/git-for-windows/git/wiki#about)). MSYS2 can be run in two flavors, [MINGW and MSYS](https://github.com/git-for-windows/git/wiki/The-difference-between-MINGW-and-MSYS2) and the flavor Git for Windows needs is MINGW. This is specified via the `MSYSTEM` variable.
+  To accommodate Git's expectations where it assumes e.g. a Unix shell to be present on the `PATH`, Git for Windows ships with a subset of [MSYS2](https://msys2.github.io/) (find out about more historical context [here](.#about.html)). MSYS2 can be run in two flavors, [MINGW and MSYS](./the-difference-between-mingw-and-msys2.html) and the flavor Git for Windows needs is MINGW. This is specified via the `MSYSTEM` variable.
 
 - **`PLINK_PROTOCOL`**
 

content/governance-model.md

@@ -54,7 +54,7 @@ project code. Contributors engage with the project through communication tools,
 [Git mailing list](mailto:[email protected]),
 [GitHub](https://github.com/git-for-windows), via [reports of issues](https://github.com/git-for-windows/git/issues)
 and via [pull requests](https://github.com/git-for-windows/git/pulls) in the issue tracker, as detailed in our
-[how to participate](https://github.com/git-for-windows/git/wiki/How-to-participate) document.
+[how to participate](./how-to-participate.html) document.
 
 Anyone can become a contributor. There is no expectation of commitment to the project, no specific
 skill requirements and no selection process. To become a contributor, a community member simply
@@ -107,11 +107,11 @@ own terms, and willing to help support other users, the community support channe
 Anyone can contribute to the project, regardless of their skills, as there are many ways to contribute.
 For instance, a contributor might be active on the project mailing list and issue tracker, or might supply
 [pull requests](https://github.com/git-for-windows/git/pulls). The various ways of contributing are described
-in more detail in our [how to participate](https://github.com/git-for-windows/git/wiki/How-to-participate) document.
+in more detail in our [how to participate](./how-to-participate.html) document.
 
 The *Git for Windows* [issue tracker](https://github.com/git-for-windows/git/issues) is the most appropriate
 place for a contributor to ask for help when making their first contribution. Please also read the projects
-[issue reporting guidelines](https://github.com/git-for-windows/git/wiki/Issue-reporting-guidelines)
+[issue reporting guidelines](./issue-reporting-guidelines.html)
 
 ## Decision-making process
 The benevolent dictatorship model does not need a formal conflict resolution process, since the

content/how-to-participate.md

@@ -20,7 +20,7 @@ A lot of documentation wants to be written, still. A good place is [Git for Wind
 Download [the SDK](https://gitforwindows.org/#download-sdk) and build Git. See the [CONTRIBUTING.md](https://github.com/git-for-windows/git/blob/HEAD/CONTRIBUTING.md) page/file
 
 
-Also have a look at [this page](https://github.com/git-for-windows/git/wiki/Building-Git) for tips and tricks revolving around building and debugging Git.
+Also have a look at [this page](./building-git.html) for tips and tricks revolving around building and debugging Git.
 
 Please also sign off your work, as [asked by the Git project](https://git-scm.com/docs/SubmittingPatches#sign-off)
 

content/install-or-update-inside-msys2-cygwin-or-git-for-windows-itself.md

@@ -3,7 +3,7 @@ title: "Install or update inside MSYS2, Cygwin or Git for windows itself"
 aliases:
   - "Install-or-update-inside-MSYS2,-Cygwin-or-Git-for-windows-itself"
 ---
-## It's different from [Install inside MSYS2 proper](https://github.com/git-for-windows/git/wiki/Install-inside-MSYS2-proper)
+## It's different from [Install inside MSYS2 proper](./install-inside-msys2-proper.html)
 
 Instead of configuring and installing Git for Windows using `pacman`, this guide introduces another approach to properly install or update Git for Windows inside MSYS2, Cygwin or even Git for Windows itself. The only thing you need is a `bash` interpreter on Windows and a `curl`.
 

content/making-a-portable-git.md

@@ -3,7 +3,7 @@ title: "Making a portable Git"
 aliases:
   - "Making-a-portable-Git"
 ---
-As the portable Git is made by putting together files from the Git SDK, it is advisable to update those files first. To update the packages, call `pacman -Syu` ([caveats apply](https://github.com/git-for-windows/git/wiki/Package-management#updating-msys2-runtime-pacman-and-bash)). If you want to test Git changes or make an portable Git from your own Git fork, you need to call `cd /usr/src/git && make install` (for documentation changes, `make install-html` and *afterwards* `prefix=/mingw64 make -C contrib/subtree install-html` - without the second `make` you get a error message about a missing `git-subtree.html` file).
+As the portable Git is made by putting together files from the Git SDK, it is advisable to update those files first. To update the packages, call `pacman -Syu` ([caveats apply](./package-management.html#updating-msys2-runtime-pacman-and-bash)). If you want to test Git changes or make an portable Git from your own Git fork, you need to call `cd /usr/src/git && make install` (for documentation changes, `make install-html` and *afterwards* `prefix=/mingw64 make -C contrib/subtree install-html` - without the second `make` you get a error message about a missing `git-subtree.html` file).
 
 To package the portable Git, install the [SDK](https://gitforwindows.org/#download-sdk), run it and then issue the following commands:
 

content/making-an-installer.md

@@ -22,7 +22,7 @@ sdk cd installer
 
 ## Detailed overview
 
-As the installer is made by putting together files from the Git SDK, it is advisable to update those files first. To update the packages, call `pacman -Syu` ([caveats apply](https://github.com/git-for-windows/git/wiki/Package-management#updating-msys2-runtime-pacman-and-bash)).
+As the installer is made by putting together files from the Git SDK, it is advisable to update those files first. To update the packages, call `pacman -Syu` ([caveats apply](./package-management.html#updating-msys2-runtime-pacman-and-bash)).
 
 If you want to test Git changes or make an installer from your own Git fork, you need to call
 

content/mapping-between-git-installer-gui-settings-and-command-line-arguments.md

@@ -22,4 +22,4 @@ The following table maps Git GUI Installation settings to corresponding Git Comm
 
 <br/>
 
-For a comprehensive list of Git for Windows Installer command line arguments [see here](https://github.com/git-for-windows/git/wiki/Silent-or-Unattended-Installation).
+For a comprehensive list of Git for Windows Installer command line arguments [see here](./silent-or-unattended-installation.html).

content/merge-conflicts-resolving-and-remembering-them.md

@@ -7,7 +7,7 @@ Work in Progress as I try and work out how to do this (06-04-2019)..
 
 When building a new release for Git-for-Windows, the full range of Windows patches the maintainer applies need to be moved ([`rebase`](https://git-scm.com/docs/git-rebase)d) from being on top of the old upstream Git, to being on top of the new upstream release.
 
-There is a [process](https://github.com/git-for-windows/git/wiki/Rebasing-Git-for-Windows), a script and the support of the merging-rebase code, but still there maybe conflicts, old and new, especially if some of the Windows code has been adopted upstream in a different form.
+There is a [process](./rebasing-git-for-windows.html), a script and the support of the merging-rebase code, but still there maybe conflicts, old and new, especially if some of the Windows code has been adopted upstream in a different form.
 
 This note looks at how to remember those resolutions, reuse them, and to learn from previous Git-for-Windows rebases.
 The magic is in the [REuse REcorded REsolution (rerere)](https://git-scm.com/docs/git-rerere) command and it's underlying database.