{"thread":{"id":"5461","subject":"Re: [RFC] gitweb wishlist and TODO list","startedAt":"2006-09-03T11:52:15Z","lastAt":"2006-09-03T12:38:48Z","messageCount":3,"participants":["Marco Costalba","Jakub Narebski"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"26264","messageId":"44fac1ee.308dbbaf.574b.08a5@mx.gmail.com","threadId":"5461","inReplyTo":null,"subject":"Re: [RFC] gitweb wishlist and TODO list","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2006-09-03T11:52:15Z","receivedAt":"2006-09-03T11:52:15Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Marco Costalba wrote:\n\n> On 9/3/06, Jakub Narebski <jnareb@gmail.com> wrote:\n>> Marco Costalba wrote:\n>>\n>>> On 9/2/06, Jakub Narebski <jnareb@gmail.com> wrote:\n>>>>\n>>>> By the way, do the diff between arbitrary revisions (say, between two\n>>>> branches/two refs) and between arbitrary versions of the same file\n>>>> would be useful to have in gitweb?\n>>>>\n>>>\n>>> A nice tool, lot of ideas to steal ;-)\n>>>\n>>>http://www.cenqua.com/fisheye/demo/viewrep/ant/src/main/org/apache/tools/ant/?FETOUR=A1\n>>\n>> FishEye? I haven't took the full tour, but the tool seems somewhat\n>> CVS centric, i.e. per file history, file description,...\n>>\n>> But for example \"breadcrumbs\" idea for the file path (each segment\n>> of path being link to given (sub)directory) is a nice one. Although \n>> if I remember correctly the pathname (for files only) is currently\n>> hack to have somewhere link to \"head\" version of current file in\n>> plain format. \n> \n> Also the UI for diff between arbitrary revisions could be interesting.\n\nThere is problem with git encouraging multiple branches and nonlinear\nhistory. While it would be fairly easy either to add Wiki-like (e.g.\nhttp://git.or.cz/gitwiki/ or http://en.wikipedia.org) radio-boxes to mark\nrevisions to compare, or add pull down menu to select revision (useless\nwith longer history) of a given file (we have diff-to-current in file\nhistory, by the way), the true power of selecting revisions to compare\nwould be when we would have graphical history visualizer built in, similar\nto gitk and qgit. \n\nBy the way, do you known any common Perl modules for generating PNG\n(graphs)?\n\nP.S. This message seems to hit VGER BOGOfilter... ehhh...\n-- \nJakub Narebski\nWarsaw, Poland\nShadeHawk on #git\n\n\n\n-- \nVGER BF report: S 0.999997\n"},{"id":"26256","messageId":"e5bfff550609030518o5e78bb05w4df4235a4931c2dd@mail.gmail.com","threadId":"5461","inReplyTo":"44fac1ee.308dbbaf.574b.08a5@mx.gmail.com","subject":"Re: [RFC] gitweb wishlist and TODO list","fromName":"Marco Costalba","fromEmail":"mcostalba@gmail.com","sentAt":"2006-09-03T12:18:33Z","receivedAt":"2006-09-03T12:18:33Z","isPatch":false,"sender":{"key":"mcostalba@gmail.com","avatar":null},"body":">\n> By the way, do you known any common Perl modules for generating PNG\n> (graphs)?\n>\n\nNo, I don't. sorry. Anyway, from my experience with qgit I can say\nthat one thing is to produce a revision graph, another thing is to\nproduce a _fast_ and (perhaps more important) no memory hogger\nrevision graph.\n\nBoth qgit and gitk implement heavy optimizations and a lot of tricks\nto make that happen. IMHO this is almost mandatory with long and\ncomplex histories like Linux tree. I'm not sure a generic graph\nbuilder is up to the task.\n\nMore, gitweb is designed to be used by many people at the same time,\nwhile qgit and gitk are for personal use only, and this adds burden\nfrom the performance/resources  point of view.\n\n\n  Marco\n\n-- \nVGER BF report: U 0.807973\n"},{"id":"26261","messageId":"edeicq$ae0$1@sea.gmane.org","threadId":"5461","inReplyTo":"e5bfff550609030518o5e78bb05w4df4235a4931c2dd@mail.gmail.com","subject":"Re: [RFC] gitweb wishlist and TODO list","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2006-09-03T12:38:48Z","receivedAt":"2006-09-03T12:38:48Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Marco Costalba wrote:\n\n>>\n>> By the way, do you known any common Perl modules for generating PNG\n>> (graphs)?\n>>\n> \n> No, I don't. sorry. Anyway, from my experience with qgit I can say\n> that one thing is to produce a revision graph, another thing is to\n> produce a _fast_ and (perhaps more important) no memory hogger\n> revision graph.\n> \n> Both qgit and gitk implement heavy optimizations and a lot of tricks\n> to make that happen. IMHO this is almost mandatory with long and\n> complex histories like Linux tree. I'm not sure a generic graph\n> builder is up to the task.\n> \n> More, gitweb is designed to be used by many people at the same time,\n> while qgit and gitk are for personal use only, and this adds burden\n> from the performance/resources  point of view.\n\nWell, I guess even if/when gitweb acquires history graph support, it would\nbe paged like history/shortlog is, i.e. at most 100 commits to graph.\n\nP.S. To those wondering why thread got broken, and why the parent post is\nlost: vger bogofilter.\n-- \nJakub Narebski\nWarsaw, Poland\nShadeHawk on #git\n\n\n\n-- \nVGER BF report: S 0.992982\n"}]}