From: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
To: git@vger.kernel.org
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Stefan Beller" <sbeller@google.com>,
"SZEDER Gábor" <szeder.dev@gmail.com>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Subject: [PATCH 0/3] nd/diff-parseopt fixups
Date: Tue, 22 Jan 2019 07:26:32 +0700 [thread overview]
Message-ID: <20190122002635.9411-1-pclouds@gmail.com> (raw)
Let me see if I could just fix up this series on top like this.
Failing this, I'll break it down and resend in small chunks.
This redoes a85e5a0108 (parse-options: allow keep-unknown +
stop-at-non-opt combination - 2019-01-17), deletes dead functions and
rewrites b9b760ed1c (diff.c: convert -B|--break-rewrites - 2019-01-17) a
bit.
Nguyễn Thái Ngọc Duy (3):
Revert "parse-options: allow keep-unknown + stop-at-non-opt
combination"
diff.c: delete unused functions
diff.c: simplify diff_opt_break_rewrites()
diff.c | 74 ++-----------------------------------------------
parse-options.c | 4 +++
2 files changed, 6 insertions(+), 72 deletions(-)
--
2.20.1.560.g70ca8b83ee
next reply other threads:[~2019-01-22 0:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 0:26 Nguyễn Thái Ngọc Duy [this message]
2019-01-22 0:26 ` [PATCH 1/3] Revert "parse-options: allow keep-unknown + stop-at-non-opt combination" Nguyễn Thái Ngọc Duy
2019-01-22 0:26 ` [PATCH 2/3] diff.c: delete unused functions Nguyễn Thái Ngọc Duy
2019-01-22 0:26 ` [PATCH 3/3] diff.c: simplify diff_opt_break_rewrites() Nguyễn Thái Ngọc Duy
2019-01-22 20:50 ` Junio C Hamano
2019-01-22 23:18 ` Junio C Hamano
2019-01-22 0:30 ` [PATCH v2 0/3] nd/diff-parseopt fixups Nguyễn Thái Ngọc Duy
2019-01-22 0:30 ` [PATCH v2 1/3] Revert "parse-options: allow keep-unknown + stop-at-non-opt combination" Nguyễn Thái Ngọc Duy
2019-01-22 0:30 ` [PATCH v2 2/3] diff.c: delete unused functions Nguyễn Thái Ngọc Duy
2019-01-22 0:30 ` [PATCH v2 3/3] diff.c: simplify diff_opt_break_rewrites() Nguyễn Thái Ngọc Duy
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=20190122002635.9411-1-pclouds@gmail.com \
--to=pclouds@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sbeller@google.com \
--cc=szeder.dev@gmail.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).