From: Junio C Hamano <gitster@pobox.com>
To: Holger Hellmuth <hellmuth@ira.uka.de>
Cc: "git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git rev-list -S ?
Date: Tue, 20 Mar 2012 13:53:14 -0700 [thread overview]
Message-ID: <7vaa3b570l.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <4F68CDA4.6060109@ira.uka.de> (Holger Hellmuth's message of "Tue, 20 Mar 2012 19:34:12 +0100")
Holger Hellmuth <hellmuth@ira.uka.de> writes:
> I read the GsoC page about the ultimate tracking tool just now and
> couldn't find the -S option in git rev-list documentation...
Slippery finger.
| $ git log -S'it drives an external
| an external' master Documentation/RelNotes
is a way to find commits that introduced and then removed the block of
text to files in the named directory, starting at the tip of 'master'.
Most of the "ultimate tracking tool" dream has already been realized in
"git blame" except one major part. Once you find where the blame lies,
the tool _could_ help the user to find where these blamed lines came from
more than it currently does. Were they typed anew? Were similar lines
removed by the commit from other files? Often people run "blame" on a
line range they are interested in, find the commits that were blamed, look
at "git show $the_found_commit" to see if they can find similar lines in
deleted parts of other files and then finally run blame again on the
deleted line range of these other files starting from the parent commit of
the found commit to do this (and this needs to be repeated). A good GUI
should be able to help this process quite a lot, if backed by a good logic
to detect "similar" code blocks.
next prev parent reply other threads:[~2012-03-20 20:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 18:34 git rev-list -S ? Holger Hellmuth
2012-03-20 20:21 ` Christopher Tiwald
2012-03-20 20:53 ` Junio C Hamano [this message]
2012-03-20 22:00 ` Jeff King
2012-03-21 11:14 ` Thomas Rast
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=7vaa3b570l.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=hellmuth@ira.uka.de \
/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).