Re: What's cooking in git.git (Jan 2016, #02; Mon, 11)

> * jc/strbuf-gets (2015-12-16) 17 commits
>  - test-sha1-array: read command stream with strbuf_getline_crlf()
>  - grep: read -f file with strbuf_getline_crlf()
>  - send-pack: read list of refs with strbuf_getline_crlf()
>  - column: read lines with strbuf_getline_crlf()
>  - cat-file: read batch stream with strbuf_getline_crlf()
>  - transport-helper: read helper response with strbuf_getline_crlf()
>  - clone/sha1_file: read info/alternates with strbuf_getline_crlf()
>  - remote.c: read $GIT_DIR/remotes/* with strbuf_getline_crlf()
>  - ident.c: read /etc/mailname with strbuf_getline_crlf()
>  - rev-parse: read parseopt spec with strbuf_getline_crlf()
>  - revision: read --stdin with strbuf_getline_crlf()
>  - hash-object: read --stdin-paths with strbuf_getline_crlf()
>  - mktree: read textual tree representation with strbuf_getline_crlf()
>  - update-index: read list of paths with strbuf_getline_crlf() under --stdin
>  - update-index: read --index-info with strbuf_getline_crlf()
>  - check-attr, check-ignore, checkout-index: read paths with strbuf_getline_crlf()
>  - strbuf: make strbuf_getline_crlf() global
> 
>  Teach codepaths that communicate with users by reading text files
>  to be more lenient to editors that write CRLF-terminated lines.
>  Note that this is only about communication with Git, like feeding
>  list of object names from the standard input instead of from the
>  command line, and does not involve files in the working tree.
> 
>  Rerolled.
>  Needs review.