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

Re: Export only modified files

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-05-18 15:15:31 CEST

On May 18, 2005, at 8:08 AM, Joe Attardi wrote:

>> Actually, I think the tool he wants is 'svn update'.
>> :-)
> 'svn update' would update your working copy with the
> changed files. What he's referring to is doing an
> export, that is, get the files out of SVN without the
> version-control "stuff" (the .svn directory, etc).

Sure, but *something* needs to know which files need to be updated.
That's why the version-control "stuff" is useful. There are 3
possible solutions, as mentioned before:

    1. Use a real working copy. It knows what it needs when you run
'svn up'. This is by far the simplest route.

    2. Use rsync. It's a bit more complex to setup, and still,
you're left with the odd question of: what are you going to rsync?
A local working copy to a remote working copy? Or will you
repeatedly 'svn export' locally, then sync it to a remote export?

    3. Write some complicated script to parse 'svn log -v', figure
out what needs updating yourself, and do it manually? This is really
hard to do.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 18 15:21:43 2005

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

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