Re: Re: "update to revision" window working copyand fully recursive difference?

On Mon, Jun 17, 2013 at 7:26 PM, gaohongyan <ghyghost_at_sohu.com> wrote:
> yes
> i don't know difference~ result is don't know use it~
>

OK, so your question, if I understand, is:

"In the 'update to revision' dialog, what is the difference between a
depth of 'working copy' and 'fully recursive'?"

If you have previously set up a "sparse checkout" by deliberately
excluding certain files or folders from your working copy, then a
depth of "working copy" will not change any of this. Updating with a
depth of "working copy" will keep your sparse checkout but get
everything else updated to the revision you specify. I'm not sure, but
I think if you have done a "switch" on a subfolder, "working copy"
depth will leave that alone as well.

If you instead choose a depth of "fully recursive", then regardless of
whether or not you have previously set up a sparse working copy, the
ENTIRE tree under the directory you update will be updated to the
revision specified. This is the recommended way to "undo" a sparse
working copy and get everything sync'd up with the same revision.

Sparse working copies are good for when you have large project trees
and only need to work on a small portion, but they sometimes get in
the way when you do things like merging.

You would do well to read the book on SVN (
http://svnbook.red-bean.com/ ). It documents the command-line tools,
but every concept there is directly applicable to TortoiseSVN commands
as well.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3058401

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-06-18 16:54:31 CEST