On Thu, 2004-07-29 at 15:45, Rick LaBanca wrote:
> I don't know any other way of putting this. I realize all of what you're
> saying. But when debugging code, and I find a chunk changed in one file, a
> way to quickly see when it changed is invaluable.
Running 'svn log foo.c' will show you every change ever made to the file
in question. Nothing will be left out. If the file exists on another
branch, you won't see the changes over on that other branch; but that's
fine, because those changes aren't in your copy of foo.c.
If, however, somebody merged changes from the other branch to your own
branch, and those changes included edits to foo.c, then 'svn log foo.c'
*will* show those changes. They've been "ported" to your branch. And
if somebody wrote a good log message ("ported rXYZ from branch to
trunk"), then you can even hunt down the original change before it was
ported.
In any case, 'svn log foo.c' shows you every change ever made to the
file in front of you. You can then 'svn diff -r X-1:X foo.c' to your
heart's content and look at every line-by-line commit to the file. You
can also run 'svn blame' (as someone mentioned), which is the equivalent
of 'cvs annotate', if you curious who wrote each line in the file.
What I'm not understanding is what's missing here. How is this
insufficent for bug hunting?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 29 22:55:52 2004