Comment 1 for bug 585509

I have the opposite problem, I need the tree to be always populated. Plugin push-and-update is what I need, but since it's client-side it needs to be installed separately everywhere I branch the repository, which is not really practical.

Since it's costly to update the working tree (as is described in the docs) I believe the default behaviour should be changed to *not* populate the tree, for local or remote repositories consistently.

Then a new option can be added, "--populate-tree" so that such behaviour is forced by the user, if needed.