Add winget installation instructions

[cvrebert]

For comparison: https://git-scm.com/download/win

[dscho]

Thank you for opening this PR.

About the content: I am not quite sure that I want to give users the impression that the winget route is a fully-supported route, though. I, for one, have neither used nor worked on it at all. So I cannot even guarantee that it installs the correct, officially-blessed version of Git for Windows...

[cvrebert]

Then it seems odd that the git-scm.com page gives equal weight to the winget route.

[dscho]

Then it seems odd that the git-scm.com page gives equal weight to the winget route.

I fully agree.

[cvrebert]

FWIW, it would make a lot of sense for g-f-w to support winget, even if only by trusting the Winget Team to get it right. Winget basically just downloads & runs your installer, and your installer doesn't seem exotic?
Winget is the first-party package manager on Windows. Surely two Windows-centric Microsoft-heavy projects should be able to get along?

To compare, it seems improbable that the upstream Git project itself is involved in the packaging for all 13 Linux/*nix distros listed on https://git-scm.com/download/linux

[rimrul]

FWIW, it would make a lot of sense for g-f-w to support winget, even if only by trusting the Winget Team to get it right.

For some definition of "get it right", probably. But their track record doesn't convince me that their broad definition of "get it right" that covers all their packages aligns with our definition of "get it right" that focuses on Git for Windows.

Winget basically just downloads & runs your installer, and your installer doesn't seem exotic?

I'm not sure they agree. The Git Winget package reliably gets stuck in automatic package verification failure limbo for about a week whenever there is a new release.

Winget is the first-party package manager on Windows.

It's kinda first-party. The client is, but the package definitions are provided by third-party contributors (with some automated checks). Their client also only works on a subset of our supported operating systems and there are at least two package managers for Windows applications that gained popularity before winget existed, struggle less with new Git for Windows releases and support more Windows versions.

Surely two Windows-centric Microsoft-heavy projects should be able to get along?

I'd say we do. I'm not aware of any hostility between us. That doesn't mean we have to endorse use of winget for what seems like barely any benefit to our users.

To compare, it seems improbable that the upstream Git project itself is involved in the packaging for all 13 Linux/*nix distros listed on https://git-scm.com/download/linux

They mostly aren't. And if Windows would've been more POSIX-ish and also would've had a proper first-party package manager with packages built from source by Microsoft back in XP or so, we probably would've never started building our own binaries and installers.