From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: git@vger.kernel.org
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Eugeniu Rosca" <erosca@de.adit-jv.com>,
"Eugeniu Rosca" <roscaeugeniu@gmail.com>,
"Jeff King" <peff@peff.net>,
"Julia Lawall" <julia.lawall@lip6.fr>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: [PATCH 0/2] diffcore-pickaxe: implement --pickaxe-raw-diff
Date: Wed, 24 Apr 2019 17:22:13 +0200 [thread overview]
Message-ID: <20190424152215.16251-1-avarab@gmail.com> (raw)
In-Reply-To: <20190424102609.GA19697@vmlxhi-102.adit-jv.com>
This implements --pickaxe-raw-diff as explained in 2/2. I based this
on "next" because Duy's in-flight diff option refactoring would have
conflicted with it.
Ævar Arnfjörð Bjarmason (2):
diffcore-pickaxe: refactor !one or !two case in diff_grep
diffcore-pickaxe: add --pickaxe-raw-diff for use with -G
Documentation/diff-options.txt | 17 ++++++++++++
diff.c | 3 +++
diff.h | 2 ++
diffcore-pickaxe.c | 48 +++++++++++++++++++++++++++-------
t/t4013-diff-various.sh | 1 +
t/t4209-log-pickaxe.sh | 45 +++++++++++++++++++++++++++++++
6 files changed, 107 insertions(+), 9 deletions(-)
--
2.21.0.593.g511ec345e18
next prev parent reply other threads:[~2019-04-24 15:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 10:26 Multi-line 'git log -G<regex>'? Eugeniu Rosca
2019-04-24 15:22 ` Ævar Arnfjörð Bjarmason [this message]
2019-04-24 15:22 ` [PATCH 1/2] diffcore-pickaxe: refactor !one or !two case in diff_grep Ævar Arnfjörð Bjarmason
2019-04-24 15:22 ` [PATCH 2/2] diffcore-pickaxe: add --pickaxe-raw-diff for use with -G Ævar Arnfjörð Bjarmason
2019-04-24 15:37 ` Ævar Arnfjörð Bjarmason
2019-04-24 22:46 ` Eugeniu Rosca
2019-04-24 23:24 ` Ævar Arnfjörð Bjarmason
2019-04-25 0:44 ` Junio C Hamano
2019-04-25 12:25 ` Ævar Arnfjörð Bjarmason
2019-05-03 9:10 ` Eugeniu Rosca
2019-05-03 8:37 ` Eugeniu Rosca
2019-04-25 0:54 ` Eugeniu Rosca
2019-04-25 12:14 ` Ævar Arnfjörð Bjarmason
2019-05-03 3:15 ` Jeff King
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=20190424152215.16251-1-avarab@gmail.com \
--to=avarab@gmail.com \
--cc=erosca@de.adit-jv.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=julia.lawall@lip6.fr \
--cc=peff@peff.net \
--cc=roscaeugeniu@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.
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).