From: Francis Moreau <francis.moro@gmail.com>
To: git@vger.kernel.org
Subject: Can't find the revelant commit with git-log
Date: Tue, 25 Jan 2011 10:01:47 +0100 [thread overview]
Message-ID: <m2ipxd2w78.fsf@gmail.com> (raw)
Hello,
I'm trying to find out a commit which removed a function inside a file.
The project is the Linux kernel, and I'm trying to look for changes
which happened between v2.6.27 and v2.6.28. The changes happened in the
following file: drivers/pci/intel-iommu.c where a function has been
removed:
$ git --version
git version 1.7.4.rc3
$ cd ~/linux-2.6/drivers/pci/
$ git grep blacklist v2.6.27 -- drivers/pci/intel-iommu.c
$
No ouput... hmm, I know it's in... oh maybe the path is incorrect
$ git git grep blacklist v2.6.27 -- intel-iommu.c
v2.6.27:intel-iommu.c:static int blacklist_iommu(const struct dmi_system_id *id)
v2.6.27:intel-iommu.c: .callback = blacklist_iommu,
ah, so Git failed previously without any comments on the wrong
path... maybe it should ?
So at that point I know that in the revision v2.6.27, there's a function
called "blacklist_iommu" in drivers/pci/intel-iommu.c
Now take a look if it's still there in v2.6.28:
$ git git grep blacklist v2.6.28 -- intel-iommu.c
$
This time nothing is printed but I know that the command is correct.
So now I'm interested in looking for the commit which removed this
function. Fo this I'm trying to use git-log(1):
$ git log --full-history --follow -S'static int blacklist_iommu(const struct dmi_system_id *id)' v2.6.27..v2.6.28 -- intel-iommu.c
$ echo $?
0
I tried different options but it fails.
Also I found that passing the exact string to '-S' is annoying, are
there any way to just pass a part of the string such as
"-Sblacklist_iommu" ?
Sorry if I miss the revelant git-log's option, but there're so many...
--
Francis
next reply other threads:[~2011-01-25 9:02 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 9:01 Francis Moreau [this message]
2011-01-25 16:12 ` Can't find the revelant commit with git-log René Scharfe
2011-01-25 17:44 ` Francis Moreau
2011-01-26 8:36 ` Francis Moreau
2011-01-26 10:44 ` Johannes Sixt
2011-01-26 20:56 ` Francis Moreau
2011-01-26 21:03 ` Sverre Rabbelier
2011-01-26 21:08 ` Francis Moreau
2011-01-26 21:14 ` Sverre Rabbelier
2011-01-26 21:31 ` Francis Moreau
2011-01-26 21:24 ` Junio C Hamano
2011-01-26 21:32 ` Francis Moreau
2011-01-26 18:11 ` René Scharfe
2011-01-28 20:29 ` René Scharfe
2011-01-29 0:02 ` Junio C Hamano
2011-01-29 2:34 ` René Scharfe
2011-01-29 5:47 ` Junio C Hamano
2011-01-29 20:26 ` René Scharfe
2011-02-01 21:28 ` Junio C Hamano
2011-02-07 22:51 ` Junio C Hamano
2011-02-10 18:50 ` René Scharfe
2011-01-29 20:26 ` René Scharfe
2011-01-28 22:01 ` René Scharfe
2011-01-29 12:52 ` Francis Moreau
2011-01-29 13:02 ` René Scharfe
2011-01-29 13:57 ` Francis Moreau
2011-01-29 15:17 ` René Scharfe
2011-01-26 9:01 ` Francis Moreau
2011-01-26 18:39 ` René Scharfe
2011-01-26 19:50 ` Francis Moreau
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=m2ipxd2w78.fsf@gmail.com \
--to=francis.moro@gmail.com \
--cc=git@vger.kernel.org \
/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).