Christiane Olschewski wrote:
>Usually all file changes in sub-directories are updated when doing SVN
>Update from top svn directory, (right-click with mouse in top svn
>directory,then choose svn update) . But sometimes subdirectories are not
>updated and not reported as having changes unless I do svn update again from
>each of the subdirectories.
>Example: if there are changes to files in 3 different subdirectories update
>from /svn/work/ may update all 3 subdirectories eg./svn/work/dir1,
>/svn/work/dir2, /svn/work/dir3, but sometimes one or more of the actually
>changed directories are left out; Workaround: update each of the
>subdirectories individually, to make sure to catch all changes.
>Is this a known bug? Any known reason?
>Thank you in advance for answers / bug fixing.
>Christiane Olschewski
>
>
>
This might be strangely related to to an incomplete commit of a tree
full of changes very recently.
One file deep in the WC folder tree failed to commit and remained
showing as changed even after all the other files committed
successfully. It was a binary file (dll) that replaced an earlier
version. To be sure it wasn't a TSVNCache issue I killed the cache.
After the new cache instance had completed it trolling the file
continued to show as changed. The file could not be committed either
until I did an update and then it committed OK. The particular folder is
one that is only ever changed when a new version of the vendor code is
release and never produced by local compilation. I have no reason to
consider that that folder alone was not fully up to date unless
something similar to what is described above has occurred.
Didn't have time to investigate further then, so your post above twigged
my memory. (TSVN rev 4653)
Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
--
Received on Wed Oct 19 10:03:23 2005