> There's a concept here that I don't seem to be communicating well.
>
> In your example, suppose you notice your 'trunk' copy of foo.c has a
> bug, and as you say, 4 changes happened to foo.c on the trunk, and 5 on
> other branches.
>
> One of two things *must* be true:
>
> 1. the buggy change happened on the trunk, or
>
> 2. the buggy change happened on a branch, then the change was ported
> to the trunk.
>
> When you run 'svn log /trunk/foo.c', you see every change that ever
> happened to the trunk-line of foo.c.
>
> If #1 is true, then the log will include the buggy change.
>
> If #2 is true, then nothing is different: the log will *still* show the
> buggy change. The change will simply have more history behind it,
> history that (if you wish) can trace back to a branch.
>
> Either way, the procedure for finding the bug is the same. It's equally
> simple.
>
> If you had the ability to ask Subversion, "show me every change that
> ever happened to foo.c on *any* branch anywhere" (just as you do with
> 'cvs history') you'd get a much larger log of changes, that's true --
> but it's just extra noise that you don't need. It's *not* helping you
> find the bug. Everything you need is already in the output of 'svn log
> /trunk/foo.c'.
I do understand, it's just harder with subversion using eclipse. The part
you are stating about the history traced to a branch is what I mean. If I
see a line has change in the trunk, That still doesn't give me the detail of
the real time it change if it's change 5 out of 25 in the branch it was
ported from.
I understand I can get that detail, but if the dev hasn't commented which
branch it came from, I have to figure that out right? Then I have to log
that branch.
just extra steps. I realize it's possible.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 30 05:51:06 2004