git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: On blame/pickaxe

From
Petr Baudis <pasky@suse.cz>
Date
Oct 16, 2006, 02:21 UTC
Message-ID
<20061016022159.GZ20017@pasky.or.cz>
In-Reply-To
<7vfydq79ae.fsf@assigned-by-dhcp.cox.net>
  Thanks for the nice writeup!

Dear diary, on Fri, Oct 13, 2006 at 03:43:46AM CEST, I got a letter where Junio C Hamano <junkio@cox.net> said that...

> When done with one parent, if you are a merge, you will then try
> to pass the blame on the remaining part that you are still
> suspected for to other parents.
  (This got me nervous but I guess it actually makes sense - if only one
parent modified a line, it's right to pass the blame up; else if you
took one parent's version verbatim, it's right to pass the blame up as
well (I think); else you've already got the blame assigned to the merge
commit and everything is all right.)
Show 7 quoted lines
> To blame the implementation of foo() to the parent, we could do
> something like this:
> 
>         for each blame_entry that you are still suspected for,
>         diff those lines (and only those lines) with the parent,
>         to see if you find a copy.  If there is a copy, you can
>         pass the blame to the parent.
  Now, this is very nifty and so for moving functions around, but I
think it is very dangerous for anything where ordering matters - large
arrays definitions, patch series files, etc. In that case, you've
completely ommitted the fact that the movement occured, which can be
crucial and based on the current behaviour of the tools, I think people
expect this now. To put it shortly, "who wrote this line" vs "who put
this line here".
  I would prefer to stay more conservative here by default. Graphical
tools could solve this by some nice presentation like
	3fea1 int moved()                         -.
	3fea1 {                                    |
	28abc 	watch(more + anime);               | 17d50
	17d50 	return !hypno;                     |
	3fea1 }                                   -'
	

Dear diary, on Sun, Oct 15, 2006 at 01:43:53AM CEST, I got a letter where Junio C Hamano <junkio@cox.net> said that...

> I have to admit that I am becoming quite fond of the name
> "pickaxe", by the way.
  Gaah, please don't. ;-)
-- 
				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*',/((..)*)$/)
Previous: Junio C HamanoNext: Junio C Hamano
Message 5 of 12 in “On blame/pickaxe”
  1. Junio C HamanoOct 13, 2006
  2. Junio C HamanoOct 13, 2006
  3. Junio C HamanoOct 14, 2006
  4. Junio C HamanoOct 14, 2006
  5. Petr BaudisOct 16, 2006
  6. Junio C HamanoOct 16, 2006
  7. Josef WeidendorferOct 16, 2006
  8. Andy WhitcroftOct 16, 2006
  9. Petr BaudisOct 17, 2006
  10. Junio C HamanoOct 21, 2006
  11. Luben TuikovOct 16, 2006
  12. Junio C HamanoOct 17, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.