GeezerVison

Why useless?

Why useless?

See: #11412

Please could you format your commit message according to the Contributing Guidelines?

Maybe something like this?

doc: correct git fix whitespace command

Refs: https://github.com/nodejs/node/issues/11412

If you don't have time it can be rewritten by whoever lands this, but if you are going to help out more on the project (as I hope you do), then it saves work if you produce better commit messages.

I reformatted commit message.

I think it should be git config --global --add apply.whitespace fix, as that fixes whitespace when you apply a patch, which is where a collaborator would need it.

It makes sense, given "Please never use GitHub's green "Merge Pull Request" button" in https://github.com/nodejs/node/blob/master/COLLABORATOR_GUIDE.md#landing-pull-requests .

@gibfahn It is ready for rereview.

Minor nit: there's a typo in the commit message (below the first line).

Minor nit: there's a typo in the commit message (below the first line).

Thanks, should be fixed now.

Landed in def78e8 with a modified commit log message.

@jasnell commit did not link?

That's odd! let's try again with the full hash def78e8
(yeah, short hash did not auto link for some unknown reason)

@jasnell yeah I've noticed it not link properly quite a few times, possibly a GitHub issue. I generally just go to https://github.com/nodejs/node and click on the Latest commit link, and then just paste in the full url (i.e. https://github.com/nodejs/node/commit/2519757b800a21c6b93490372841bc58307c46b7), that way you know it worked.

Maybe we are starting to be out of seven-character hashes and there was an ambiguity. FWIW, I copy the full commit hash via git rev-parse HEAD | pbcopy on macOS (I believe git rev-parse HEAD | xclip -selection clipboard should do the same on Linux) right after committing to master.

UPD: nope, no ambiguity, that's the only commit to start with def78e8.