From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jan 2016, #02; Mon, 11)
Date: Tue, 12 Jan 2016 09:39:53 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1601120939270.2964@virtualbox> (raw)
In-Reply-To: <xmqqlh7vvfxc.fsf@gitster.mtv.corp.google.com>
Hi Junio,
On Mon, 11 Jan 2016, Junio C Hamano wrote:
> * 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.
Actually, it waits for a re-roll ;-)
Ciao,
Dscho
next prev parent reply other threads:[~2016-01-12 8:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 23:45 What's cooking in git.git (Jan 2016, #02; Mon, 11) Junio C Hamano
2016-01-12 0:06 ` Mike Hommey
2016-01-12 3:04 ` Junio C Hamano
2016-01-12 4:34 ` Edmundo Carmona Antoranz
2016-01-12 8:39 ` Johannes Schindelin [this message]
2016-01-12 18:47 ` Junio C Hamano
2016-01-12 21:49 ` Jeff King
2016-01-13 23:07 ` Junio C Hamano
2016-01-13 23:22 ` Jeff King
2016-01-13 23:44 ` Junio C Hamano
2016-01-13 23:54 ` Junio C Hamano
2016-01-14 10:21 ` Jeff King
2016-01-13 2:56 ` David A. Greene
2016-01-18 13:35 ` Michael J Gruber
2016-01-18 17:06 ` Jeff King
2016-01-18 21:39 ` Eric Wong
2016-01-19 7:07 ` Michael J Gruber
2016-01-25 9:56 ` Duy Nguyen
2016-01-25 22:03 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1601120939270.2964@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).