Hello Johan,
>
> -----Original Message-----
> From: johan556@gmail.com [mailto:johan556@gmail.com]
> Sent: 31 January 2007 13:24
> To: users@subversion.tigris.org
> Subject: Re: "svn log" not reaching revision 1
>
>
>
> > On 1/31/07, Rob Hubbard <Rob.Hubbard@celoxica.com> wrote:
> > The "svn mv" commands are significant. It may be that "trunk/subdir" existed back to revision 1 (even if it has been moved), but that the trunk into which it has been moved does not. Was the "trunk" directory *created* (without being moved or copied from something else) at around revision 900?
>
> Yes I think you are right. I guess the the significant revisions are those given below (note that the actual subdir name is "tcs" and not "subdir" as in my previous example).
>
> ======================
> r903 | holmberg | 2006-10-11 09:36:17 +0200 (on, 11 okt 2006) | 2 lines
> Changed paths:
> A /base/trunk/tcs (from /base/trunk/trunk:902)
> D /base/trunk/trunk
> -----------------------------------
> r902 | holmberg | 2006-10-11 09:35:54 +0200 (on, 11 okt 2006) | 2 lines
> Changed paths:
> D /base/tcs/trunk
> A /base/trunk/trunk (from /base/tcs/trunk:901)
> -----------------------------------
> r901 | holmberg | 2006-10-11 09:34:38 +0200 (on, 11 okt 2006) | 2 lines
> Changed paths:
> A /base/trunk
> ======================
>
> I made those changes rather "naively" in the repository browser of TortoiseSVN. I had no idea that it should have such consequences.
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".
> > Note that "http://svn.server/my/proj/trunk " may not be the same object in different revisions. Have a read of the SVN book about peg revisions.
>
> Thanks for the tip. I'll have to read it carefully later to understand if it applies to my current situation.
The reason for mentioning peg revisions is as follows:
Assuming that the root of your repos is at http://svn.server/base/, try
svn ls -r900 http://svn.server/base/tcs/trunk
and you'll be told that it doesn't exist, because this means
svn ls -r900 http://svn.server/base/tcs/trunk@HEAD
The message will be something like
"svn: File not found: revision 900, path '/tcs/trunk'"
Then try
svn ls -r900 http://svn.server/base/tcs/trunk@900
or
svn ls -r900 http://svn.server/base/trunk/tcs
and I think these will both give you a listing, and of the same thing.
The first says: give me the object from revision 900 (-r900) that was called "tcs/trunk" in revision 900 (@900). The latter says give me the object from revision 900 that is now (at the HEAD) called "trunk/tcs" (whatever it was called then).
Note that SVN will be able to follow histories through moves and copies only backwards through the revisions (or "time"), not forwards. This will doubtless change when proper rename support has been implemented.
Hope that helps (and hope I've got the details right),
Rob.
_____________________________________________________________________
This message has been checked for all known viruses by the MessageLabs Virus Scanning Service, on behalf of Celoxica Ltd.
This email and any files transmitted with it are confidential and
may be legally privileged. It is intended solely for the use of the
individual or entity to whom it is addressed. If you have received
this in error, please contact the sender and delete the material
immediately. Whilst this email has been swept for viruses, you
should carry out your own virus check before opening any
attachment. Celoxica Ltd accepts no liability for any loss or
damage which may be caused by software viruses or interception
or interruption of this email.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 31 15:54:18 2007