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

Re: [PATCH] Avoid errors from git-rev-parse in gitweb blame

From
RGRafael Garcia-Suarez <rgarciasuarez@gmail.com>
Date
Jun 3, 2008, 14:40 UTC
Message-ID
<b77c1dce0806030740td820c52ve45619812313776c@mail.gmail.com>
In-Reply-To
<200806031614.29161.jnareb@gmail.com>
2008/6/3 Jakub Narebski <jnareb@gmail.com>:
Show 8 quoted lines
>> 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.)

Show 12 quoted lines
> 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.
Previous: Jakub NarebskiNext: Jakub Narebski
Message 10 of 40 in “Avoid errors from git-rev-parse in gitweb blame”
  1. Avoid errors from git-rev-parse in gitweb blameRafael Garcia-Suarez, Jun 3, 2008
  2. Lea WiemannJun 3, 2008
  3. Jakub NarebskiJun 3, 2008
  4. Rafael Garcia-SuarezJun 3, 2008
  5. Jakub NarebskiJun 3, 2008
  6. Rafael Garcia-SuarezJun 3, 2008
  7. Jakub NarebskiJun 3, 2008
  8. Rafael Garcia-SuarezJun 3, 2008
  9. Jakub NarebskiJun 3, 2008
  10. Rafael Garcia-SuarezJun 3, 2008
  11. Jakub NarebskiJun 3, 2008
  12. Rafael Garcia-SuarezJun 3, 2008
  13. Jakub NarebskiJun 3, 2008
  14. Luben TuikovJun 3, 2008
  15. Luben TuikovJun 3, 2008
  16. Luben TuikovJun 3, 2008
  17. Jakub NarebskiJun 3, 2008
  18. Junio C HamanoJun 4, 2008
  19. Jakub NarebskiJun 4, 2008
  20. Junio C HamanoJun 5, 2008
  21. 1/2 git-blame: refactor code to emit "porcelain format" outputJunio C Hamano, Jun 5, 2008
  22. Jakub NarebskiJun 6, 2008
  23. 2/2 blame: show "previous" information in --porcelain/--incremental formatJunio C Hamano, Jun 5, 2008
  24. Jakub NarebskiJun 6, 2008
  25. Junio C HamanoJun 6, 2008
  26. Jakub NarebskiJun 6, 2008
  27. Jakub NarebskiJun 6, 2008
  28. Luben TuikovJun 4, 2008
  29. Lea WiemannJun 3, 2008
  30. Jakub NarebskiJun 3, 2008
  31. Lea WiemannJun 3, 2008
  32. Jakub NarebskiJun 4, 2008
  33. Lea WiemannJun 4, 2008
  34. Jakub NarebskiJun 4, 2008
  35. Lea WiemannJun 8, 2008
  36. Jakub NarebskiJun 8, 2008
  37. Luben TuikovJun 3, 2008
  38. Jakub NarebskiJun 3, 2008
  39. Luben TuikovJun 3, 2008
  40. Jakub NarebskiJun 3, 2008

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.