CODEWITHSUNDEEP
svnversion-controlrepositorytortoisesvn
teenup
teenup

Reputation: 7667

How to force mark folder as up to date with head revision without taking svn update/checkout when we know the files are all already identical?

I have a path say 'A' on subversion repository in which I want to make some changes but do not want to commit the changes inside 'A' again.

I have following on my system:

I take following steps:

How can I force subversion to mark 'Y' folder on my system up-to-date with 'B' on repository without taking any update from 'B' as it already has identical files with 'B'?

Upvotes: 1

Views: 132

Answers (3)

Dennis C
Dennis C

Reputation: 24747

If they are SAME repository, SAME version and SAME branch. I guess you could just delete your 'B' and do a full recursion copy (cp -a) from 'A', including hidden folders and meta files.

SVN checkout do more then a download copy, it fetch and compare version and cache latest HEAD.

I could suggest you go for a git solution, using git-svn as a proxy copy and just use git on your working folder.

Upvotes: 1

Eugene
Eugene

Reputation: 656

A second thought - instead of svn copy and export you might just copy locally whole working copy with all svn metadata to a different location and update it occasionally

Upvotes: 1

Eugene
Eugene

Reputation: 656

If you already copied A with svn copy on remote server, svn doesn't really COPY data there, it just create pointers to old data. When updating working copy, to optimize network operations it will just make local copy of old data to new location. Then just commit main files, not branches. like

svn ci trunk

leaving branch version uncommited

I've found good article covering new svn functionality

http://blogs.collab.net/subversion/reducing_network_traffiic_in_subversion_1-8

Upvotes: 1

Related Questions