I believe the proposed fix is to change the default value of 'bzr init-repo' to include --trees. (rather than being --no-trees).
Alternatively, maybe we could make the default be based on whether the target location is local or remote.
Either way, this has probably gotten a little bit worse, because of the URL and encoding fixes, they now get a URL:
liliana % bzr add foo
bzr: ERROR: No WorkingTree exists for file:///home/jameinel/dev/bzr/%2Ctmp/c/xxyy/.bzr/checkout/.
I believe the proposed fix is to change the default value of 'bzr init-repo' to include --trees. (rather than being --no-trees).
Alternatively, maybe we could make the default be based on whether the target location is local or remote.
Either way, this has probably gotten a little bit worse, because of the URL and encoding fixes, they now get a URL: /home/jameinel/ dev/bzr/ %2Ctmp/ c/xxyy/ .bzr/checkout/ .
liliana % bzr add foo
bzr: ERROR: No WorkingTree exists for file://