Tor Ringstad <torhr@pvv.org> writes:
> The background for the question was that I'm toying around with some
> ideas for "persistent changelists" aka "shelves", and being able to
> create a branch from the BASE of a WC with local changes seemed to be
> a good starting point.
>
> The next question is if the following command line is actually
> supposed to do what I'm expecting of it:
>
> % cd <WC-root>
> % svn cp -rBASE . svn://somehost/somerepo/branches/mybranch
>
> That is, should it
>
> 1) create a copy that exactly reflects the state of my WC *without*
> local changes, including any mixed revisions and/or switches, or
>
> 2) create a copy of "." as seen in its BASE revision?
>
> Or put another way, should "BASE" be evaluated for the top-level of
> the copy operation only, or individually for each of the sub-targets?
Your summary question at the end reverses the order of the two
proposed behaviors you listed, but yes, it should be (1) -- copy the
complex mixed revisions, switches, etc. And if you eliminate the
"-rBASE", it should apply your local mods after doing copies of the
base revisions -- in other words, technically it should be possible to
recover your local diff from a branch created with:
$ svn cp . svn://somehost/somerepo/branches/mybranch
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 22 19:56:09 2007