[MERGE][0.15] Hide commands for nested trees.

Martin Pool martinpool at gmail.com
Tue Mar 13 07:59:27 GMT 2007

On 13/03/07, Robert Collins <robertc at robertcollins.net> wrote:
]> > The easiest way is probably to split that kind-detection behaviour
> > into a different workingtree class, which can remain experimental for
> > this release.
> >
> > Are you confident in keeping join in the non-reference mode or should
> > we hide that too?
> I'd rather we dont have a new format here, I think having a new feature
> which is available by choice (must explicitly upgrade to it), is fine.
> nested-trees are already implicitly disabled for vanilla knit
> repositories.

Just to be clear; Robert changed the kind-detection so that the
workingtree only considers directories to be subtrees if the
repository supports subtrees.  So although WorkingTree4 is now the
default, it should not activate subtree support until you also use the
non-default repository.

So if subtrees are likely to confuse or hurt people, there is some
protection, but of a somewhat indirect kind.  But if you think they
are still very rough this may not be enough: people might use new
branches for speed, and then hit subtree bugs.  In that case perhaps
we should have a separate format.


More information about the bazaar mailing list