Re: On blame/pickaxe

From: Petr Baudis <pasky@suse.cz>
Date: Oct 17, 2006, 00:44 UTC
Message-ID: <20061017004429.GC20017@pasky.or.cz>
In-Reply-To: <453393E5.3020203@shadowen.org>

Dear diary, on Mon, Oct 16, 2006 at 04:15:01PM CEST, I got a letter where Andy Whitcroft <apw@shadowen.org> said that...

Show 8 quoted lines

> Josef Weidendorfer wrote:
> > Hi,
> > 
> > this blame-passing thing really looks very promising and powerful.
> > 
> > On Monday 16 October 2006 08:43, you wrote:
> >> If the user is not prepared to see code movement, pickaxe can be
> >> run without -M nor -C to get the classic blame output.

Ok, so in this case -M and -C does not mean just looking for copies/movements in other files but inside the same file as well.

Perhaps we might want to differentiate those two cases since searching in all files might be significantly slower.

Show 9 quoted lines

> > Another blame-passing heuristic would be very interesting for code:
> > "Ignore white-space changes".
> > This way, commits which only do some reindentations simply are skipped.
> > 
> > It looks like such a thing would just be a matter of passing "-b" to
> > executions of "diff" in the blame-passing algorithm.
> 
> I am thinking that that is probabally going to need to be optional, for
> example python the indentation is everything to the meaning of the code.

(OTOH, just today I was retrieving some code from deep inside a script to a common function, which of course caused massive indentation shift. So it is very desirable in order to catch these. But more we get involved in this, the more we will probably want to know about the syntax of the content we are digging in.)

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
#!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1
lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)