Missing documentation upstream? (Document how $HOME is set on Windows)

[alejandro5042]

• I was not able to find an open or closed issue matching what I'm seeing

Migrating the discussion in a commit comment to an issue.

Here's what @hickford said in 4931518#commitcomment-149554802:

@alejandro5042 @dscho Any idea why this paragraph doesn't appear at https://git-scm.com/docs/git ? Does the change have to be upstreamed to https://github.com/git/git/blob/master/Documentation/git.txt ?

I'll be honest, I'm not sure. Maybe it's cause this is the Windows version of Git, and perhaps this functionality wasn't upstream?

Here's what I'm finding:

• My original commit was back in March 2018 in 6e494ad
• However, the Windows functionality was upstreamed July 2019 in git@e12a955

Seems like that July 2019 commit should have included my documentation change.

[dscho]

Any idea why this paragraph doesn't appear at https://git-scm.com/docs/git ? Does the change have to be upstreamed to https://github.com/git/git/blob/master/Documentation/git.txt ?

Yes, and yes ;-)

Here's what I'm finding:

• My original commit was back in March 2018 in 6e494ad
• However, the Windows functionality was upstreamed July 2019 in git@e12a955

Seems like that July 2019 commit should have included my documentation change.

Too true.

A lot of Git for Windows' patches have to be upstreamed, and I'll be honest with you: The reason why I don't spend more time on upstreaming these patches is the process that requires sending patches to a mailing list where reviewers' priorities seem to diverge from mine...

If you want to take some of that burden from my shoulders, I would be delighted.

[hickford]

Upstream PR at gitgitgadget#1834 ready to send

[dscho]

This PR was merged (or more correctly: The Git project, being still a fan of mailing lists, applied the patches exported from that PR and created completely new commits that were then merged).