mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Eugeniu Rosca <>
To: Junio C Hamano <>, <>
Cc: Eugeniu Rosca <>,
	Eugeniu Rosca <>
Subject: Multi-line 'git log -G<regex>'?
Date: Wed, 24 Apr 2019 12:26:09 +0200	[thread overview]
Message-ID: <> (raw)

Hello git community,

In the context of [1], I would like to find all Linux commits which
	'devm_request_threaded_irq(* IRQF_SHARED *)'
	'devm_request_threaded_irq(* IRQF_ONESHOT *)'

Actually, I would be happy with a much lower degree of precision, e.g.
finding commits which _removed_ IRQF_SHARED and _added_ IRQF_ONESHOT.

I am aware of the difference between `git log -G` and `git log -S`, but
these two options alone don't seem to help me in this particular
scenario. Is there any git built-in way to achieve my goal?

    ("[v4,1/2] thermal: rcar_gen3_thermal: fix interrupt type")

Best regards,

             reply	other threads:[~2019-04-24 10:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-24 10:26 Eugeniu Rosca [this message]
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

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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

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).