On Wed, Aug 19, 2009 at 12:19 AM, Daniel Becroft<djcbecroft_at_gmail.com> wrote:
> This might be an obvious question, but is your working copy pointing at
> trunk? Is it possible your WC has been switched (somehow) to be pointing at
> a branch?
This is a fresh project, currently we don't have a branches or tags
yet hence there are empty folders only...
Possible is everything ;-) Please find out my reply in thread "We
could not find some revision in SVN repository" from yesterday at
22:44. There is the procedure I had to undertake to resynchronize my
client with server.
1. During described procedure when I was "removing" non-existing
subfolders and files from the repository and added them from the
scratch, I did not change the path
2. To check out sources mentioned in my previous reply I used
CollabNet command line client into temporary location passing URL via
command line, hence AFAIK it should be completely independent on
TortoiseSVN client and status of my current WC (as I wrote: I created
batch to check out sources into temporary location and compare them
with my current WC to verify, whether all files are in the repository
and have the same content to guarantee that everybody will check out
the same project's snapshot as I have.
> Right-click on the WC directory, go Properties, and then
> Subversion tab. The URL field at the top will tell you where you're
> committing to.
URL points to the same location as every time I inspected its value
and every time I committed my changes.
> What is shown under the 'Check for Modifications' dialog?
Currently I see a status corresponding to changes I did: two modified
files and two new non-versioned folders with few new files I'm
currently working on.
If path were changed (and probably were because of few revisions AFTER
Tortoise client fallen out of step have been commited two levels up
from different machines) , IMHO it could happened only internally,
because nobody of us has changed path manually and all consecutive
commitments after resynchronizing WC with repository continue working
with CORRECT path without changing URL.
It seems there is a problem if folder does not exists in the
repository (no mattter how it happened) and client still has this
folder in the cache?
Perhaps an URL of file being commited is incorrectly built if this
happens or is incorrectly interpreted on server side?
Thanks for your help, Petr
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-08-19 12:43:56 CEST