Preparing for 2.20.1 brown-paper-bag maintenance release

Here is an excerpt from a draft edition of "What's cooking" report for topics that are about an immediate 2.20.1 maintenance release, with five topics that I plan to merge to 'next' and then to 'maint' soonish (they're all marked as "Will merge to 'next' and then to 'master'").

They'll be in 'pu' but not in 'next' in today's pushout, but unless I hear breakage reports in time, I am hoping to merge them to 'next' during tomorrow's integration cycle, so that we can start the new week with 2.20.1.

Thanks.

--------------------------------------------------

* ds/hash-independent-tests-fix (2018-12-12) 1 commit
 - .gitattributes: ensure t/oid-info/* has eol=lf

 Test portability fix.

* jc/run-command-report-exec-failure-fix (2018-12-12) 1 commit
 - run-command: report exec failure

 A recent update accidentally squelched an error message when the
 run_command API failed to run a missing command, which has been
 corrected.

* nd/show-gitcomp-compilation-fix (2018-12-12) 1 commit
 - parse-options: fix SunCC compiler warning

 Portability fix for a recent update to parse-options API.

* js/help-commands-verbose-by-default-fix (2018-12-12) 2 commits
 - help -a: handle aliases with long names gracefully
 - help.h: fix coding style

 "git help -a" did not work well when an overly long alias is
 defined, which has been corrected.

* js/mailinfo-format-flowed-fix (2018-12-13) 1 commit
 - t4256: mark support files as LF-only

 Test portability fix.