Migrate the wiki pages #59
Conversation
…ion whether those versions actually introduced bugs rather than fixing them
There seems to be a strong preference by the MSYS2 project to have it in all-capital letters. Signed-off-by: Johannes Schindelin <[email protected]>
Colons are not allowed in Windows filenames... Signed-off-by: Johannes Schindelin <[email protected]>
…dicting emphasis. This better communicates that the surrounding sentence emphasizes the preceeding, rather than mollifying it
Signed-off-by: Johannes Schindelin <[email protected]>
Git for Windows' wiki pages were moved as part of git-for-windows/git-for-windows.github.io#59. Let's adjust the FAQ URL that pointed to the wiki. Signed-off-by: Johannes Schindelin <[email protected]>
|
Only managed a quick check, the https://github.com/git-for-windows/git-for-windows.github.io/blob/main/index.html link is currently 404 (I had google searched for pages with the start http bit), but the above mentioned PR may fix that. My only bookmark (https://github.com/git-for-windows/git/wiki/FAQ) , which was to the FAQs does provide an proper page that gives the redirect. I tried a number of the pages linked on the right-hand drop-down list on https://github.com/git-for-windows/git/wiki/FAQ and did not find any that were 404 (missing) or didn't give unexpected results. |
No, that As such, I don't think that any original link to https://github.com/git-for-windows/git-for-windows.github.io/blob/main/index.html would be worth preserving.
I verified those manually (by running |
This is a follow-up for git-for-windows/git-for-windows.github.io#59.
Git for Windows' wiki pages were migrated in git-for-windows/git-for-windows.github.io#59.
Git for Windows' wiki pages were migrated in git-for-windows/git-for-windows.github.io#59.
Git for Windows' wiki pages were migrated in git-for-windows/git-for-windows.github.io#59.
Git for Windows' wiki pages were migrated in git-for-windows/git-for-windows.github.io#59.
Git for Windows' wiki pages were migrated in git-for-windows/git-for-windows.github.io#59.
Git for Windows' wiki pages were migrated in git-for-windows/git-for-windows.github.io#59.
Git for Windows' wiki pages were migrated in git-for-windows/git-for-windows.github.io#59.
Git for Windows' wiki pages were migrated in git-for-windows/git-for-windows.github.io#59.
Git for Windows' wiki pages were migrated in git-for-windows/git-for-windows.github.io#59.
Git for Windows' wiki pages were migrated in git-for-windows/git-for-windows.github.io#59.
Git for Windows' wiki pages were migrated in git-for-windows/git-for-windows.github.io#59.
Git for Windows' wiki pages were migrated in git-for-windows/git-for-windows.github.io#59.
Git for Windows' wiki pages were migrated in git-for-windows/git-for-windows.github.io#59.
Git for Windows' wiki pages were migrated in git-for-windows/git-for-windows.github.io#59.
Git for Windows' wiki pages were migrated in git-for-windows/git-for-windows.github.io#59.
Theoretically, a wiki is a nice thing to have. Many fly-by contributions make it fun and a useful resource.
However, reality is a thing. The vast majority of contributions Git for Windows' wiki receives are spam and vandalism, and often incorrect information is added. This is a huge burden.
That burden would be bearable if only the benefit outweighed the cost, but that is not so: While working on this PR, I noticed quite a bit of totally outdated and superseded information, e.g. information about the way Git for Windows' CI builds work, information about using Vagrant (which is no longer supported, and I do not even remember how long ago said support was dropped), information about the
vs/mainbranch (which no longer exists), etc. I have edited the CI page in this PR, but it would make reviewing much harder if I had continued to clean up, so I'll do that later in a separate PR.In git-for-windows/git#4951, I started a weather balloon, to see whether we could move the information there, or at least mirror it and lock down the wiki. But it is a poor habitat for those pages because it would add quite a chunk of patches that would have to be rebased frequently.
Therefore, I needed a better solution, and I think this here PR is it. It moves the information from the wiki to Git for Windows' home page, making it easier to access and at this day and age it shouldn't be asking too much to require edits via the usual PR experience (there is even the option to edit the files directly on github.com in a web UI).
After merging this here PR, I will still need to make a (scripted) commit and push it to the wiki so that all of the pages' content is replaced with links to the respective new location of said information.
"625 commits, are you nuts, Johannes?" I almost hear you say.
Well, it is not actually that bad. The vast majority of these commits are straight from the wiki, and only the last 19 commits need to be reviewed, really, i.e. 79e4d9d...e1add09
But maybe before that, it would be a good idea to have a peek at https://dscho.github.io/git-for-windows.github.io/sitemap.html to see how the pages will look. Personally, I am quite happy with the result, it looks much more pleasant than the drab wiki pages currently look. Plus: In this repository, with the full power of Hugo at our disposal, we have much more liberty to change the look in whatever way we like.