[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Strange behaviour (sparse update oder bug ?)

From: wp1110314-johann <johann.letzel_at_johann-letzel.de>
Date: Tue, 22 Jun 2010 09:43:27 +0200

Tested with TortoiseSVN 1.6.7 and 1.6.8. Server is SVN 1.5.2 under Linux.
Take following scenario:

- Repository with subfolder "SUB" with one file in it "OLD"
- Working copy is at head revision (e.g. 50)
- Create new file "ADD1" in "SUB"
- Add it and commit (rev 51)
- Modify "OLD" and commit (rev 52)
- Create file "ADD2" in "SUB", add it and commit (rev 53)
- Modify "ADD1" and commit (rev 54)

- Switch working copy to revision 50
- on "SUB" "Check from modifications"->"Check repository":

  SUB modified
  ADD1 added
  ADD2 added
  OLD modified

- Select "ADD2" and "update" to revision 53
- "ADD2" is added to directory "SUB"
- "SUB" now has revision 53
- on "SUB" "Check from modifications"->"Check repository":

  OLD modified

- Where is "ADD1" !?
- "Update" on "SUB" (to head revision)

   Update
   C:\playground\SUB\OLD
   File 'ADD1' in directory 'C:\playground\SUB' is not a versioned
resource

I also checked this sceanrio with Subclipse and Subversive. Both made it
right because they didn't rise the revision of the folder.

Is it a bug ?

Regards

Johann Letzel

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2624463

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-06-22 09:52:09 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.