S.Ramaswamy S wrote:
On 4/20/05, Heikki Toivonen <[EMAIL PROTECTED]> wrote:
* 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
The issue isn't really about what is possible - even with cvs things are
possible from command line, it's just really painful.
svn log does not seem to support date range like this: now -6h
The format of svn log is not easy to read.
There is no fast way of switching between the log and looking at
different diffs (all, just one file, just one checkin, just one checkin
to one file)
* 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
But first you need to determine suspected range, which is another set of
commands. And backouts are really rare, so you never remember the syntax
without getting some help.
* 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.
I don't know if svn log supports excluding files based on regex.
I don't see how to limit this to a person.
'svn blame' does that though it doesn't do mouse-overs : ) .
viewcvs also does this except for mouse overs; I find it really handy to
browse files this way, to understand why things were coded the way they
were.
* 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.
Providing link from viewcvs would be easy, though.
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.
Bonsai is written in Perl. SVN Bonsai in Python.
--
Heikki Toivonen
signature.asc
Description: OpenPGP digital signature
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
