All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Kastrup <dak@gnu.org>
To: Thomas Rast <tr@thomasrast.ch>
Cc: git@vger.kernel.org
Subject: Re: Is there something like a blamed diff?
Date: Mon, 17 Feb 2014 12:02:31 +0100	[thread overview]
Message-ID: <8761oeuhmg.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87ioseujej.fsf@thomasrast.ch> (Thomas Rast's message of "Mon, 17 Feb 2014 11:24:04 +0100")

Thomas Rast <tr@thomasrast.ch> writes:

> David Kastrup <dak@gnu.org> writes:
>
>> When comparing two branches, decorating the flat diff with the
>> respectively responsible commits seems like it would be nice to do/have
>> (the blame on the identical parts, in contrast, is not really
>> interesting).  Is there any tool that provides something like that?
>
> This seems to come up every year or so:
>
> http://thread.gmane.org/gmane.comp.version-control.git/110369/focus=110383

Nice.  That one could likely be sped up by calling git-blame just once
on each file with multiple -L options.

Though actually with the current implementation of git-blame you are
likely faster for a large number of differences by doing each region
separately anyway since then the cost for digging through the history is
obviously O(n) for n consecutive runs on n chunks while the
administrative overhead for several chunks in a single run is O(n^2) at
the moment.

-- 
David Kastrup

  reply	other threads:[~2014-02-17 11:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-15 18:38 Is there something like a blamed diff? David Kastrup
2014-02-17 10:24 ` Thomas Rast
2014-02-17 11:02   ` David Kastrup [this message]
2014-02-17 17:41     ` 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=8761oeuhmg.fsf@fencepost.gnu.org \
    --to=dak@gnu.org \
    --cc=git@vger.kernel.org \
    --cc=tr@thomasrast.ch \
    /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.