2008/6/3 Jakub Narebski <jnareb@xxxxxxxxx>: >> Shameless plug : the sources for perl 5 are currently being kept in a >> perforce repository. There is a rough web interface to it at >> http://public.activestate.com/cgi-bin/perlbrowse with excellent blame >> log navigation features (including navigation against p4 >> integrations). > > By the way, what is the difference between '<<' links and 'br' link > in the above mentioned annotate/blame interface? "br" navigates to another branch from which this file has been integrated (in p4 speak.) > I'd like to say that I prefer gitweb's marking blame by blocks, not by > lines, and extra info on mouseover. But having blame navigation > capability of perforce web interface would be really nice (I think > "git gui blame" has something like this; I don't know about other > tools like qgit, giggle, or ugit). > >> Since we're going to move the official perl 5 vcs to git (many many >> thanks to Sam Vilain for that, BTW), > > BTW. how in your opinion Git compares to Perforce, both as a tool > itself, and also about quality of companion tools such like gitweb > or git-gui? I'm not using companion tools much, but I'm really impatient to switch to git. (I'm often working offline and applying patches from mailboxes. That already makes two good reasons for switching:) > I think it would be really nice. Will you want to use git-diff-tree > to mark differences from the version we came from (marked by 'hp', > 'hpb' and 'fp' URI parameters), or would you rather extend git-blame? I don't know. I'll look at git-diff-tree. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
