From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH 0/4] Blame in reverse
Date: Thu, 03 Apr 2008 02:08:45 -0700 [thread overview]
Message-ID: <7v4paj486a.fsf@gitster.siamese.dyndns.org> (raw)
This is still rough, but I think it would be a good foundation to build
interesting archaeology tools on.
Usual "git blame" starts from the latest revision and finds where each
line came from (i.e. who came up with that brilliant idea, or more often
who introduced that bug). This new mode starts from an old revision, and
annotates in reverse --- up to which point each line survived, before it
got replaced with something else. A line that began its life in one file
can be removed from the original file but migrate to another, and we will
find its final resting place when you use the usual -C -C option.
[1/4] "log" and friends: --children option
[2/4] builtin-blame.c: move prepare_final() into a separate function.
[3/4] builtin-blame.c: allow more than 16 parents
[4/4] git-blame --reverse
builtin-blame.c | 206 +++++++++++++++++++++++++++++++++++++++----------------
log-tree.c | 20 ++++++
revision.c | 28 ++++++++
revision.h | 1 +
4 files changed, 196 insertions(+), 59 deletions(-)
next reply other threads:[~2008-04-03 9:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 9:08 Junio C Hamano [this message]
2008-04-03 9:12 ` [PATCH 1/4] "log" and friends: --children option Junio C Hamano
2008-04-03 19:58 ` Johannes Schindelin
2008-04-03 9:13 ` [PATCH 2/4] builtin-blame.c: move prepare_final() into a separate function Junio C Hamano
2008-04-03 9:14 ` [PATCH 3/4] builtin-blame.c: allow more than 16 parents Junio C Hamano
2008-04-03 9:19 ` [PATCH 4/4] git-blame --reverse Junio C Hamano
2008-04-03 11:25 ` [PATCH 0/4] Blame in reverse Johannes Sixt
2008-04-03 19:47 ` Junio C Hamano
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=7v4paj486a.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.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).