Greg Hudson <ghudson@MIT.EDU> writes:
> 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 suggested this on IRC and people were a little skeptical, though not
> exactly against it. I thought I would propose it on the list, and
> then file an enhancement issue if there is some support and no
> objections.
To me it feels a bit overspecialized, complex to explain, and easy for
users to get wrong.
"This is like 'svn export', except it updates an existing working
copy, but that working copy may have no local modifications, it
must really, really be an exact match to revision X."
It moves against the trend of Subversion keeping track of its own
state and Doing The Right Thing automatically (i.e., without
increasing the burden on the user). Finally, the entire feature will
become pointless when we implement (as we someday surely will) working
copies with optional text-bases.
Personally, I'd rather see us solve the general problem, and not add
special code to handle one specific case.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Nov 8 17:54:34 2004