Steve Greenland <steveg@lsli.com> writes:
> The command 'cvs log foo.c' shows the entire log for foo.c, including
> all branches.
>
> The command 'svn log foo.c' shows only from the tip of the current
> branch. For example, if I'm working on a branch, and there's a commit to
> the trunk, I don't see that log message with any variation of svn log
> options that I've been able to determine. Worse, if I merge the branch
> into the trunk, and then 'svn log foo.c' on the trunk, I don't see the
> messages from the commit on the trunk, only the message for the commit
> after the merge. Apparently, I must either gather up and duplicate the
> messages, or have people chase them down by hand.
>
> FWIW, I understand why this is easy in CVS (all history in single RCS
> file), and not in Subversion (which would require chasing down and back
> up all the copies, etc.) Is there a command/option in svn that will do
> the necessary chasing? Or has someone written a tool to do it?
There isn't a nicely packaged solution for this yet, though there
might be some scripts that parse the output of 'svn log -v' (or
something similar), and DTRT.
Mike Pilato <cmpilato@collab.net> says he has a script that does
something similar, that would help you. It needs cleaning up and
documenting, but if you poke him, he might be willing to do that and
put it in our contrib/ dir. I hereby hand thee the Poking Stick :-).
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Sep 1 18:13:18 2004