From: Thomas Rast <trast@student.ethz.ch>
To: Samuel Lucas Vaz de Mello <samuellucas@datacom.ind.br>
Cc: git@vger.kernel.org, Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: Blamming a diff between two commits?
Date: Tue, 17 Feb 2009 15:09:18 +0100 [thread overview]
Message-ID: <200902171509.21434.trast@student.ethz.ch> (raw)
In-Reply-To: <499AB8A1.7090909@datacom.ind.br>
[-- Attachment #1: Type: text/plain, Size: 1908 bytes --]
Samuel Lucas Vaz de Mello wrote:
> Is there any way to git blame (or annotate) a diff between two
> commits?
Piecing it together from existing tools isn't really hard, and made
for a nice distraction.
Call it as './git-blame-diff.perl HEAD^ HEAD' or so.
This lacks proper argument checking and a chdir to the repository top
level. Maybe you could fill in the gaps and shape it as a contrib
patch? For bonus points, change it so that the workdir version can be
used as the new side of the diff, by omitting the second argument.
--- 8< ---
#!/usr/bin/perl -w
sub parse_hunk_header {
my ($line) = @_;
my ($o_ofs, $o_cnt, $n_ofs, $n_cnt) =
$line =~ /^@@ -(\d+)(?:,(\d+))? \+(\d+)(?:,(\d+))? @@/;
$o_cnt = 1 unless defined $o_cnt;
$n_cnt = 1 unless defined $n_cnt;
return ($o_ofs, $o_cnt, $n_ofs, $n_cnt);
}
sub get_blame_prefix {
my ($line) = @_;
$line =~ /^([0-9a-f]+\s+\([^\)]+\))/ or die "bad blame output: $line";
return $1;
}
my ($oldrev, $newrev) = @ARGV;
open($diff, '-|', 'git', '--no-pager', 'diff', $oldrev, $newrev) or die;
my ($pre, $post);
my $filename;
while (<$diff>) {
if (m{^diff --git ./(.*) ./\1$}) {
$filename = $1;
} elsif (m{^(\+\+\+|---) ./$filename$}) {
# ignore
} elsif (m{^@@ }) {
my ($o_ofs, $o_cnt, $n_ofs, $n_cnt)
= parse_hunk_header($_);
my $o_end = $o_ofs + $o_cnt;
my $n_end = $n_ofs + $n_cnt;
open($pre, '-|', 'git', 'blame', "-L$o_ofs,$o_end",
$oldrev, '--', $filename) or die;
open($post, '-|', 'git', 'blame', "-L$n_ofs,$n_end",
$newrev, '--', $filename) or die;
} elsif (m{^ }) {
print get_blame_prefix(scalar <$pre>), "\t", $_;
scalar <$post>; # discard
} elsif (m{^\-}) {
print get_blame_prefix(scalar <$pre>), "\t", $_;
} elsif (m{^\+}) {
print get_blame_prefix(scalar <$post>), "\t", $_;
}
}
--
Thomas Rast
trast@{inf,student}.ethz.ch
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-02-17 14:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 13:16 Blamming a diff between two commits? Samuel Lucas Vaz de Mello
2009-02-17 13:53 ` Johannes Schindelin
2009-02-17 14:09 ` Samuel Lucas Vaz de Mello
2009-02-17 14:27 ` Johannes Schindelin
2009-02-17 14:03 ` Matthieu Moy
2009-02-17 14:09 ` Thomas Rast [this message]
2009-02-20 20:04 ` Thomas Rast
2009-02-22 12:32 ` Jan Hudec
2009-02-22 18:49 ` Matthieu Moy
2009-02-22 19:11 ` Jan Hudec
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=200902171509.21434.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=samuellucas@datacom.ind.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.