ESCape "\n" codes

[gvanem]

In a .nf section, Groff / Troff will display a:

 printf("Errno: %ld\n", error);

as:

  printf("Errno: %ld0, error);

when a "\n" is not escaped. Use "\\n" instead.

[bagder]

The change looks fine, but please make your commit message follow our standard style. Perhaps:

 CURLINFO_OS_ERRNO.3: escape "\n" codes

[bagder]

The change looks fine, but please make your commit message follow our standard style. Perhaps:

 CURLINFO_OS_ERRNO.3: escape "\n" codes

[gvanem]

Too late to edit the commit message now. Only the title is editable. At least here on Github.

[bagder]

You can always edit the commits in your branch (git rebase -i) and then force-push them to the branch. But once they're merged to master it is too late.

[gvanem]

There's an option here on Github for a Create a merge commit. But it's disabled for curl:

So I'm not sure what to do. Or what you want me to do about this PR.

[kdudka]

@gvanem git rebase -i is a command that you need to run in a terminal.

[gvanem]

@kdudka I know that. But it's a big hassle for me to git pull , edit, commit and push just for this small change. That's why I did it all here at Github (it was easier to contribute to libcurl in the old pre-git days).

[bagder]

I disagree with that, but perhaps the biggest change and improvement compared to the "old days" and now is that we run a bazillion tests on the change before we merge it...

I squashed and forced-pushed these commits with a new commit message!