git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Rast <trast@student.ethz.ch>
To: Semyon Kirnosenko <semyon.kirnosenko@gmail.com>
Cc: <git@vger.kernel.org>
Subject: Re: [BUG] difference of info from diff and blame
Date: Tue, 11 Jan 2011 14:40:08 +0100	[thread overview]
Message-ID: <201101111440.08619.trast@student.ethz.ch> (raw)
In-Reply-To: <4D2C333A.3010401@gmail.com>

Semyon Kirnosenko wrote:
[Word wrap fixed.]
> 
> I have jquery repo (https://github.com/jquery/jquery.git)
> Let's get blame for some file in some revision:
> git blame -l -s 2ad223aedd1f93c783d98d60adc9fda3bdfbb4b6 -- src/event/event.js
> According to blame, line 127 was added in revision 
> 2ad223aedd1f93c783d98d60adc9fda3bdfbb4b6.

The surrounding context (with authorship and some whitespace snipped,
obviously it's always the same) is

2ad223ae (124)		
2ad223ae (125)		// Pass along a fake event
2ad223ae (126)		data.unshift( this.fix({ type: type, target: element }) );
2ad223ae (127)
2ad223ae (128)		// Trigger the event
2ad223ae (129)		if ( (val = this.handle.apply( element, data )) !== false )
2ad223ae (130)			this.triggered = true;


> Let's get diff for that revision:
> git diff-tree -p 2ad223aedd1f93c783d98d60adc9fda3bdfbb4b6 -- src/event/event.js
> We can see this:
> @@ -105,19 +120,16 @@ jQuery.event = {
> 
>   		// Handle triggering a single element
>   		else {
> -			var handler = element["on" + type ], val,
> -				fn = jQuery.isFunction( element[ type
> +			var val, ret, fn = jQuery.isFunction( element
> +			
> +			// Pass along a fake event
> +			data.unshift( this.fix({ type: type, target:
> 
[this blank context line is line 127 in the postimage]
> -			if ( handler ) {
> 
> As you can see line 127 is not marked with '+' char, which means it was 
> not added in this revision. But blame sad otherwise.

git-blame internally runs a diff with no context lines to "pass
blame".  On all lines in this diff, the current commit can pass on
blame to the parent, thus avoiding having to take it for itself.

And indeed, running

  git show -U0 2ad223ae -- src/event/event.js

in your repository gives a hunk

@@ -108,11 +123,8 @@ jQuery.event = {
-			var handler = element["on" + type ], val,
-				fn = jQuery.isFunction( element[ type ] );
-
-			if ( handler ) {
-				// Pass along a fake event
-				data.unshift( this.fix({ type: type, target: element }) );
-	
-				// Trigger the event
-				if ( (val = handler.apply( element, data )) !== false )
-					this.triggered = true;
-			}
+			var val, ret, fn = jQuery.isFunction( element[ type ] );
+			
+			// Pass along a fake event
+			data.unshift( this.fix({ type: type, target: element }) );
+
+			// Trigger the event
+			if ( (val = this.handle.apply( element, data )) !== false )
+				this.triggered = true;

So I would tend to agree with the blame implementation.  If anything
it's a bug in git-diff when not using any context.

Do you have a reproduction recipe that exhibits the flaw on a
non-whitespace line?  I'm not up to speed on the diff implementation
(maybe someone else can help?), but I wouldn't be too surprised if it
had heuristics that put lines consisting only of whitespace at a lower
importance than "actual" lines.

-- 
Thomas Rast
trast@{inf,student}.ethz.ch

  reply	other threads:[~2011-01-11 13:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11 10:38 [BUG] difference of info from diff and blame Semyon Kirnosenko
2011-01-11 13:40 ` Thomas Rast [this message]
2011-01-12  7:53   ` Semyon Kirnosenko
2011-01-12 10:20     ` diff -U0 occasionally misses a chance to make empty lines context [was: Re: [BUG] difference of info from diff and blame] 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=201101111440.08619.trast@student.ethz.ch \
    --to=trast@student.ethz.ch \
    --cc=git@vger.kernel.org \
    --cc=semyon.kirnosenko@gmail.com \
    /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).