Don't understand why checkout depth defaults to "working copy only"

[muttley69]

Is my development pattern unusual ? All I ever want is to keep an entire tree
of a particular branch on my local computer. These projects aren't too big.

The only checkout depth I will ever want is "fully recursive".

I understand why people will want other things, but why is "fully recursive"
not the default ? Surely, that's the most "obvious" way people would expect
it to work.

Having to manually select "fully recursive" every time I do anything is very
error-prone. How to set the default to "fully recursive" ?

Is there something unusual about my development pattern, to not want
"working copy only" ? If so, how *should* I be doing it ?

I tried setting "make depth sticky" but that does something else ?

RMW


--
View this message in context: http://old.nabble.com/Don%27t-understand-why-checkout-depth-defaults-to-%22working-copy-only%22-tp34132840p34132840.html
Sent from the tortoisesvn - users mailing list archive at Nabble.com.

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

To unsubscribe from this discussion, e-mail: [users-un...@tortoisesvn.tigris.org].

[Simon Large]

On 9 July 2012 09:22, muttley69 <r...@sevrin.co.uk> wrote:
> Is my development pattern unusual ? All I ever want is to keep an entire tree
> of a particular branch on my local computer. These projects aren't too big.
>
> The only checkout depth I will ever want is "fully recursive".
>
> I understand why people will want other things, but why is "fully recursive"
> not the default ? Surely, that's the most "obvious" way people would expect
> it to work.

It is the default, and that is what most people use all the time.

> Having to manually select "fully recursive" every time I do anything is very
> error-prone. How to set the default to "fully recursive" ?

Right click on the root of your working copy, Update to Revision and
set the depth there to Fully Recursive and Make Depth Sticky.

The default in most commands may come up as Working Copy. That just
means it will respect the depth that is already set, so once you have
set Fully Recursive, then any updates you do will be exactly that.

The reason the default is Working Copy and not Fully Recursive is so
that people who have sparse working copies do not have to keep
changing that value to avoid getting a fully recursive checkout. It
keeps the last (sticky) setting you used, so it should work well for
all use cases.

> Is there something unusual about my development pattern, to not want
> "working copy only" ? If so, how *should* I be doing it ?
>
> I tried setting "make depth sticky" but that does something else ?

Simon

--
: ___
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net

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

[David Balažic]

Simon Large

Thanks for the explanation. This puzzled me too.

Especially, since a description like "Remember this setting" would seem
more logical to me than "Make depth sticky".

Regards,
David

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

[Niemann, Hartmut]

>
> Right click on the root of your working copy, Update to Revision and
> set the depth there to Fully Recursive and Make Depth Sticky.
>
> The default in most commands may come up as Working Copy. That just
> means it will respect the depth that is already set, so once you have
> set Fully Recursive, then any updates you do will be exactly that.
>
> The reason the default is Working Copy and not Fully Recursive is so
> that people who have sparse working copies do not have to keep
> changing that value to avoid getting a fully recursive checkout. It
> keeps the last (sticky) setting you used, so it should work well for
> all use cases.

Is there a reason why there is no "sticky" checkbox for the
checkout command and the default behaviour is "not sticky"?

I did an initial checkout "immediate children" of a project
and then a "sticky" update of two (of several) subfolders "fully recursive".
When I updateted the root of this WC, it started pulling in all other
folders.
It looks like I have to do three steps:
* checkout "immediate children"
* update to revision (HEAD), "immediate children, sticky" (which does nothing but store the depth)
* update the interesting children to revision (HEAD) "fully recursive, sticky"
and the second of these steps is not really intuitive.

"Omit externals" is not sticky either. Why? I have a use case where
it makes sense to decide for every working copy whether the externals
are needed. (And the externals are huge ...)

Am I doing anything wrong here?

With best regards
Hartmut

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