From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/6] post-strbuf_getline cleanups
Date: Sun, 31 Jan 2016 06:22:16 -0500 [thread overview]
Message-ID: <20160131112215.GA4589@sigill.intra.peff.net> (raw)
As promised, here are the "how about this on top" patches that came out
of the discussion for the "strbuf_getline" series in:
http://thread.gmane.org/gmane.comp.version-control.msysgit/21773/focus=284001
As I looked further at some of the option-parsing cleanups, I realized
that some of them are more than cleanups; we're actually fixing bizarre
behavior and segfaults.
[1/6]: give "nbuf" strbuf a more meaningful name
[2/6]: checkout-index: simplify "-z" option parsing
[3/6]: checkout-index: handle "--no-prefix" option
[4/6]: checkout-index: handle "--no-index" option
[5/6]: checkout-index: disallow "--no-stage" option
[6/6]: apply, ls-files: simplify "-z" parsing
-Peff
next reply other threads:[~2016-01-31 11:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-31 11:22 Jeff King [this message]
2016-01-31 11:25 ` [PATCH 1/6] give "nbuf" strbuf a more meaningful name Jeff King
2016-01-31 11:54 ` Johannes Schindelin
2016-01-31 11:59 ` Jeff King
2016-01-31 12:01 ` Johannes Schindelin
2016-01-31 11:25 ` [PATCH 2/6] checkout-index: simplify "-z" option parsing Jeff King
2016-01-31 11:26 ` [PATCH 3/6] checkout-index: handle "--no-prefix" option Jeff King
2016-01-31 11:29 ` [PATCH 4/6] checkout-index: handle "--no-index" option Jeff King
2016-02-01 2:25 ` Junio C Hamano
2016-02-01 3:22 ` Jeff King
2016-01-31 11:30 ` [PATCH 5/6] checkout-index: disallow "--no-stage" option Jeff King
2016-02-01 2:18 ` Junio C Hamano
2016-02-01 3:18 ` Jeff King
2016-01-31 11:35 ` [PATCH 6/6] apply, ls-files: simplify "-z" parsing Jeff King
2016-01-31 11:59 ` Johannes Schindelin
2016-02-01 21:47 ` Junio C Hamano
2016-02-01 22:52 ` Junio C Hamano
2016-02-02 5:29 ` Jeff King
2016-02-01 2:14 ` [PATCH 0/6] post-strbuf_getline cleanups 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160131112215.GA4589@sigill.intra.peff.net \
--to=peff@peff.net \
--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.
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 NNTP newsgroup(s).