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

Re: Problem with svn checkout url@rev

From: Yves Bergeron <yves.bergeron_at_shq.gouv.qc.ca>
Date: 2006-04-13 16:44:07 CEST

>>> Ryan Schmidt <subversion-2006Q1@ryandesign.com> 04/13/06 10:31 am
>>>
On Apr 13, 2006, at 16:10, Yves Bergeron wrote:

>> I'm using Subversion 1.3.1 (server on Solaris 9; client 1.3.0 on
>> Windows) and today I noticed what seems to be a bug.
>>
>> When I do a svn checkout http://serveur:port/svn/repos --revision
>> 123, I get what I want. That is revision 123 of my repository.
>>
>> When I do a svn checkout http://serveur:port/svn/repos@123, I
>> always get the head revision.
>>
>> What is strange is that the command seems to check if the specified

>> revision exists before extracting the head revision. If I do a svn

>> checkout http://serveur:port/svn/repos/sub-dir@n, if sub-dir
>> doesn't exist for the revision n, there is an error. If it exists,

>> I get the head revision.
>>
>> So, is it me or is there really a bug ?

>As far as I can tell, you're describing exactly how Subversion is
>designed to behave. Have you read about the difference between peg
>and operative revisions and what they're each for?

>http://svnbook.red-bean.com/nightly/en/svn.advanced.pegrevs.html

I've just read an interesting thread on the subjet:
http://subversion.tigris.org/servlets/ReadMsg?list=users&msgNo=46560

 
It seems that the concept of peg revisions is not clear for everyone.
What I learned is that --revision and @revision is not the same. For my
needs, I will use --revision.
 
Thank you.

« Le présent courriel peut contenir des renseignements confidentiels et ne s'adresse qu'au destinataire dont le nom apparaît ci-dessus. Si ce courriel vous est parvenu par mégarde, veuillez le supprimer et nous en aviser aussitôt. Merci. »
Received on Thu Apr 13 16:47:37 2006

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.