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

Curiosity on copying working copies

From: David Summers <david_at_summersoft.fay.ar.us>
Date: 2004-05-22 03:25:09 CEST

Hola Subversionistas, :-)

Typically, if I don't have the specific branch or tag of a Subversion
working copy but do have another one, I'll do a "cp -r oldwc newwc" and
then "svn status", and then "svn switch NEWURL" to the new one to save
having to go through the (relatively) long checkout across the Internet.

Specifcally, for instance, I just updated my subversion-1.0.x branch
"cd subversion-1.0.x; svn update; cd .." and then "cp -r subversion-1.0.x

Then, I do a "svn status" and ALWAYS (so far since I can remember) it

$ svn st
M subversion/bindings/com/SVN.rgs
M subversion/bindings/com/SVNCOM.def
M subversion/bindings/com/SVNStatus.rgs
M subversion/bindings/com/SVNCOMps.def
M subversion/bindings/com/SVNCOM.idl
M subversion/bindings/com/resource.h
M subversion/bindings/com/SVNCOMps.mk

I go and check the source of the copy and there are no modifications.

What is special about the subversion/bindings/com/* files and why does it
ALWAYS show them as modified but no other files?

Not a problem, just one "svn revert subversion/bindings/com/*" to fix it
but it is very curious to me.


David Wayne Summers          "Linux: Because reboots are for hardware upgrades!"
david_at_summersoft.fay.ar.us   PGP Key: http://summersoft.fay.ar.us/~david/pgp.txt
PGP Key fingerprint =  C0 E0 4F 50 DD A9 B6 2B  60 A1 31 7E D2 28 6D A8 
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat May 22 03:25:24 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.