Hi -
I'm using the following version of Tortoise on Windows XP
---------------------------------------------------------
TortoiseSVN 1.4.1, Build 7992 - 32 Bit , 2006/11/11 09:34:39
Subversion 1.4.2,
apr 0.9.12
apr-iconv 0.9.7
apr-utils 0.9.12
berkeley db 4.4.20
neon 0.26.2
OpenSSL 0.9.8d 28 Sep 2006
zlib 1.2.3
---------------------------------------------------------
Until recently both repository and my working directories resided on the
same network filesystem on the same logical drive mapping (J). (using
file:/// syntax for the repository location, not using http:)
A few weeks ago I relocated the repository to another fileserver, still
using the file:/// syntax to define the repository location, but this
time the logical mapping is to drive Z. My working copy is still in its
original location (J).
I also keep a second working copy on my local harddrive (C) as
additional security.
Since moving the repository to Z, I've noticed that after I successfully
commit a change to the repository from my working copy on J, if I then
immediately do a right-click "SVN Update" on the top directory of the
working copy on C, it updates C not to the new head revision (n) , but
to the previous head revision (ie n -1). If I repeat the update, it
makes no difference. However if I close Windows Explorer and open a new
explorer window and then do the update again, it updates to the correct
(new) head revision (n). It seems that explorer is not registering the
change of head revision after a commit.
The same thing happens if, after a successful commit from working copy
J, I choose the "SVN Update" menu option to update the J working copy
(ie the one where I've just submitted the change from). I would expect
that it would find no changes to apply, since J was the source of the
latest commit. However, it instead reverts J to the previous head
revision, undoing the changes that have just been submitted!
My workarounds to this are either to close and re-open Windows explorer,
or to make a note of the new head revisions number and then use the
"update to revision" option on the tortoise sub-menu and explicitly
enter the new revision number. (if I just try the "head" revision option
I still have the same problem of it choosing the wrong version).
I'm using the same version of Tortoise on another machine, but for a
completely separate project where the repository and working copy are on
the same drive and use the file:/// protocol to access the repository
(ie same as my original setup described above) and I've not encountered
these problems there at all.
Thanks for your time.
Chris Gould
Enterprise Data Management
FIL - Systems
Mailzone : XTW7A
internal: 8-724-7787
external: + 44 (0)1737 837787
Important: Fidelity Investments International, Fidelity Investment
Services Limited, Fidelity Pensions Management and Financial
Administration Services Limited (a Fidelity Group company) are all
authorised and regulated in the UK by the Financial Services Authority
and have their registered offices at Oakhill House, 130 Tonbridge Road,
Hildenborough, Tonbridge, Kent TN11 9DZ. Tel 01732 361144. Fidelity only
gives information on products and does not give investment advice to
private clients based on individual circumstances. Any comments or
statements made are not necessarily those of Fidelity. The information
transmitted is intended only for the person or entity to which it is
addressed and may contain confidential and/or privileged material. If
you received this in error, please contact the sender and delete the
material from any computer. All e-mails sent from or to Fidelity may be
subject to our monitoring procedures. Direct link to Fidelity's website
- <http://www.fidelity-international.com/world/index.html>
Received on Mon Jan 15 14:51:29 2007