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

Re: repo structure change and external definitons

From: Ryan Schmidt <subversion-2010d_at_ryandesign.com>
Date: Wed, 24 Nov 2010 17:57:10 -0600

>> Von: Ryan Schmidt [mailto:subversion-2010d_at_ryandesign.com]
>> Gesendet: Wednesday, November 24, 2010 12:52 PM
>> An: Schroeder, Hartmut
>> Cc: users_at_subversion.apache.org
>> Betreff: Re: repo structure change and external definitons
>> On Nov 24, 2010, at 05:00, Schroeder, Hartmut wrote:
>>> say,
>>> svn list http://server/repo/trunk/a/b/c
>>> gives:
>>> d/
>>> in revision 100.
>>> Then:
>>> svn del http://server/repo/trunk/a/b/c/d
>>> (r101)
>>> Then, the checkout
>>> svn co -p 100 http://server/repo/trunk/a/b/c/d
>>> won't work, but with the peg revision
>>> svn co http://server/repo/trunk/a/b/c/d@100
>>> it does.
>>> All external definitons using '-p 100 http://server/repo/trunk/a/b/c/d'
>>> won't work anymore and need to be changed. That leeds to heavy
>>> discussions cause some teams here using a lot of external definitons and
>>> run into that problem.
>>> We are using Subversion 1.5.5
>>> Does a reason exist for that behaviour?
>>> Is it a point of change in upcoming releases?
>>> Is there a nice workaround?
>>> Or, is the only solution to use always peg revisions in external
>>> definitions?
>> For exactly the reasons you've discovered, you should always use peg revisions in externals definitions.
On Nov 24, 2010, at 07:28, Schroeder, Hartmut wrote:

> it would be a good idea to update the documentation, first to give a big warning if one moves or deletes an entry and second to recommend externals definitons only with peg revisions. today that is not the case.

That sounds like a good idea to me. The book has its own mailing list and issue tracker where you could bring this issue to the authors' attention.
Received on 2010-11-25 00:57:56 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.