>> That's what I did. The problem is that I had a checked out working
>> copy of the older tag. When I then updated this copy with the now
>> new "current" tag it only updated the existing files. But there were
>> also new files in the new tag and they didn't get created in the
>> existing working copy. Only when I checked out anew I also got
>> the new files (don't know about deleted files, didn't test yet).
>>
>> cvs update had a switch -d to create directories which were new
>> in the repo. But I couldn't find a similar switch for svn update.
>> Anyway, the new files were in an existing directory, so I would
>> have needed a flag to update also new files.
>>
>> So: should it work to update and get new files or do I need to do a
>> new checkout? Updating from the trunk usually also gets new
>> files so it generally works fine.
>
>So, checking out a clean work directory was fine. Doing an "svn
>update" on the old work directory had problems.
>
>You may need to do a "svn switch" even though the URL is actually the
>same. I don't know enough of Subversion's internals to understand how
>it tracks the URL, but I suspect that that the old working directory
>is still pointing to the old tag directory and not the new one.
Well, it can't be that a user always has to "switch" to the same tag
he supposedly is already on. I mean, that's what update is for, no?
I will do some more testing. Thanks for the help though.
bye Fabi
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 29 16:00:33 2005