Re: "svn log" not reaching revision 1

Thanks to everybody who answered to my questions. I now better
understand the "mechanics" of why Subversion behaves like it does.

On 1/31/07, Rob Hubbard <Rob.Hubbard@celoxica.com> wrote:
> >
> > I made those changes rather "naively" in the repository browser
> > of TortoiseSVN. I had no idea that it should have such consequences.
>
["svn log" output removed]
>
> I don't think there's anything *wrong* with what you've done.
> Assuming that I've read revisions 901 to 903 correctly, they
> effectively just rename or move "base/tcs/trunk" to "base/trunk/tcs".
>

Exactly. That was my intention.

After doing some further experiments, I think the crucial thing I
didn't understand before was the following fact:

    when a directory is moved inside another directory,
    the log entries of files inside the first directory "disappear" *when
    viewed with "svn log" from the second directory*.
    Only the fact that the first directory was moved inside the
    second directory is visible as a revision.

A good example is when two separate projects are merged. Suppose for
example that we have two project in the repository with the following
layout:

    A/
    A/trunk
    B/
    B/trunk

and want to change the structure to

    A_and_B/
    A_and_B/trunk/
    A_and_B/trunk/A
    A_and_B/trunk/B

If my current understanding is correct, it is *impossible* to arrive
at the new layout in such a way that a "svn log" in the
"A_and_B/trunk" directory will show "old" changes in for example
"A/trunk" (before the merge).

Even if I now understand how Subversion works, I can't help but
thinking that the behaviour is counter-intuitive (at least to me).

> Hope that helps (and hope I've got the details right),
> Rob.

Yes, thanks for answering .

/Johan

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 2 22:15:31 2007