Hmm.. I see your point. But doesn't this then invalidate the
clarification that copy is "with history"? If it were with history, then
essentially the entire repository would behave, post copy, as if the
branch existed back in revision 50 as well?
Dale Worley wrote:
>>From: Greg Fodor [mailto:greg@parature.com]
>>
>>Ie, if I branch the trunk at revision 100, check out
>>a working
>>copy of the branch, I am unable to update to any revision
>>before 100 on
>>that branch from there on out. For example, performing 'svn update -r
>>50' on the branch's working copy. Instead, I get the
>>(uninformative :( )
>>error message "Cannot replace a directory from within."
>>
>>
>
>That's not very surprising. Because of the location of the file in question
>in your WC, and the Subversion URL that was checked out to make the WC, you
>are asking for revision (e.g.) 50 *of a particular file name*. And there
>was no file of that name in revision 50. In revision 50, there was a file
>of a different name that is the ancesor of your file name in revision 100,
>but that's something different.
>
>Dale
>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: users-help@subversion.tigris.org
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jul 5 17:45:24 2005