[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

svn:externals revision pegging problem

From: Baranowski, Daniel <dbaranowski_at_LSIJAX.COM>
Date: Tue, 11 Mar 2008 11:05:19 -0400

Hi All,


I've checked the lists and I haven't seen any one with this same
problem, so I'm assuming I'm doing something wrong.


I have an external in my trunk, the property looks like this:

MyExternal -r 125 https://ourserver/path/to/repo/sub/folder


Now, when in trunk I do an update, I get the MyExternal directory at
revision 125. This is great, this is what I want!


Now, if I cd into MyExternal and do an update, I get HEAD. This is not
great, and this is not what I want :(


I can go back and for between trunk and MyExternal doing update and each
time it will update to either revision 125 or HEAD depending on where
I'm doing the update from.


Is there something that I'm doing wrong, is this just how it works, or
is this a bug?





Disclaimer - This email and any files transmitted with it are proprietary and may contain privileged or copyright information. You must not present this message to another party without
gaining permission from the sender. If you are not the intended recipient you must not copy, distribute or use this email or the information contained in it for any purpose other than to notify
us. If you have received this message in error, please notify the sender immediately, and delete this email from your system. We do not guarantee that this material is free from viruses or any
other defects although due care has been taken to minimize the risk. eSafe scanned this email for viruses, vandals and malicious contentAny views expressed in this message are those of
the individual sender, except where the sender specifically states them to be the views of LSI.
Received on 2008-03-11 16:05:51 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.