On 4/20/05, Heikki Toivonen <[EMAIL PROTECTED]> wrote: > > Not primarily a GUI, although GUI is a nice to have. I think GUI will > make many tasks that I am interested in much faster. > > Here are some scenarios: > > * Show me all the checkins in the last 6 hours: I want to see who > checked in, what files were changed, what were the checkin comments. I > want quick access to diffs to any file that I am interested in, of those > checkins.
svn log can do that - check out Revision dates section from the svn book: http://svnbook.red-bean.com/en/1.1/svn-book.html#svn-ch-3-sect-3.3 > > * Two days from now we realize that one of my changes today broke a > feature and we want to back it out. What revision was that? What command > do I issue to back it out? Run svn log -v -rSuspected_range ; once you have determined the revision you can do a reverse merge, followed by a commit. That should roll back the bad revision. http://www.onlamp.com/pub/a/onlamp/2004/08/19/subversiontips.html?page=2 > > * Two months from now we find a regression bug, and using some older > builds we narrow the breakage down to a few day window of checkins. Show > me all the checkins, maybe limited by a directory, in this time period: > who checked in, what were the checkin comments, what are the diffs? > Limit this further by who checked in. And don't list image files. 'svn log' again - the cvs log was nowwhere near. > > All of those should be possible starting from the Bonsai query > interface. It didn't seem that svn log, svnlook and svn admin would be > very effective tools in doing these tasks. svnadmin is mainly for admin tasks and svnlook can be used locally on the svn host to poke around repositories. > > Bonsai has also some other features that are lacking in viewcvs, > although at least some of these should be easy to add, and some close > equivalents are available in smart desktop GUIs. These are not > showstoppers and I don't really expect SVN Bonsai to provide these, at > least not in the beginning. > > * Let me change the diff parameters. > > * Show me an annotated source file so that I can see for each line who > checked in, and can quickly check the checkin comment by mousing over > the person/revision. 'svn blame' does that though it doesn't do mouse-overs : ) . > > * Provide quick links to cvsgraph and lxr This is one area where you may not find much support, esp. given the way subversion treats branches and tags - i.e. as copies. It's not easy to answer the question "On what branches and tags does this file exist ? " - there is no svn cmd to do that at present. svn also does not do merge tracking at present. BTW, (a) if the Bonsai sprint is about modifying Bonsai to support these features, then you might want to consider the svn-python bindings ; I don't know what Bonsai is written in (b) Trac makes extensive use of the svn python bindings and is an open source issue tracker with python integration, but I guess your choice is already made. Ramaswamy > > * Enable me to make an HTML link that goes to to a specific revision of > a file, and causes scroll to a line while highlighting it. > > * I much prefer the Bonsai view of just showing the checkin history in a > nice table compared to viewcvs' cluttered default view of a file. > Compare > http://bonsai.osafoundation.org/cvslog.cgi?file=chandler/parcels/osaf/framework/blocks/calendar/CalendarCanvas.py&root=/usr/local/cvsrep > to > http://cvs.osafoundation.org/viewcvs.cgi/chandler/application/Application.py > > -- > Heikki Toivonen > > > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > > Open Source Applications Foundation "Dev" mailing list > http://lists.osafoundation.org/mailman/listinfo/dev > > > > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
