From: Jeff King <peff@peff.net>
To: Eugeniu Rosca <roscaeugeniu@gmail.com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
git@vger.kernel.org, "Junio C Hamano" <gitster@pobox.com>,
"Julia Lawall" <julia.lawall@lip6.fr>,
"Eugeniu Rosca" <erosca@de.adit-jv.com>
Subject: Re: [PATCH 2/2] diffcore-pickaxe: add --pickaxe-raw-diff for use with -G
Date: Thu, 2 May 2019 23:15:31 -0400 [thread overview]
Message-ID: <20190503031531.GA19436@sigill.intra.peff.net> (raw)
In-Reply-To: <20190425005448.GA6466@x230>
On Thu, Apr 25, 2019 at 02:54:48AM +0200, Eugeniu Rosca wrote:
> > This is unrelated to --pickaxe-raw-diff, -U<n> just implies -p in
> > general. See e.g. "git log -U1".
>
> Oops. Since I use `-U<n>` mostly with `git show`, I missed the
> implication. You are right. Then, my question is how users are
> going to (quote from commit description):
>
> > >> > [..] search [..] through an arbitrary amount of
> > >> > context lines when combined with -U<n>.
>
> and achieve a `git log --oneline` report, given that -U<n> unfolds
> the commits?
You can use "-s" to suppress patch output; as long as it comes after -U
on the command-line, it will countermand the patch-format part.
(Of course it doesn't matter until we have a raw-diff grep, since
otherwise the context lines do not matter at all, and you should just
omit -U entirely).
-Peff
prev parent reply other threads:[~2019-05-03 3:15 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 ` [PATCH 0/2] diffcore-pickaxe: implement --pickaxe-raw-diff Ævar Arnfjörð Bjarmason
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 [this message]
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=20190503031531.GA19436@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=avarab@gmail.com \
--cc=erosca@de.adit-jv.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=julia.lawall@lip6.fr \
--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).