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

Re: RFC: "svn export -r X:Y" to update an existing export

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2004-11-08 15:03:46 CET

Greg Hudson <ghudson@MIT.EDU> wrote on 11/07/2004 03:42:04 PM:

> Sometimes people like to keep an up-to-date checkout of their
> repository around for reference purposes. Such a checkout is never
> modified and never has mixed revs. It also isn't precious; if it gets
> corrupted due to an accidental modification or interrupted operation,
> it can be tossed out and recreated at the expense of some time.
>
> It might be nice if people could do this without paying the fairly
> heavy space and time penalty associated with working copy
> administrative files. My idea is to make "svn export -r X:Y" update a
> presumed existing export at rX to match rY. It would be up to the
> user to keep track of the rev the tree is currently at.

I think this could be very useful. I know a lot of people have asked for
a "shadow directory" feature as exists in VSS and PVCS. This gets a lot
closer, while adding some flexibility. I could envision people that are
using Subversion to manage a web site using this feature to manage the
content of the web site.

Why did you make the comment about the output not being "precious"? Do
you view any aspect of this command as perhaps being unreliable? I guess
it certainly is relying on the user to feed in the correct inputs to the
command to get the right output, but assuming that is taken care of, I
would imagine the results of running this command would be as reliable as
any other.

I assume that Y could be HEAD or perhaps even omitted to represent HEAD?
If using a value of HEAD, would the command output the value of Y in a way
that it could be captured and stashed away for the next run?

Thanks

Mark

_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Nov 8 15:04:10 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.