Comment 2 for bug 414305
Revision history for this message
| John A Meinel (jameinel) wrote Re: [Bug 414305] Re: branching from a 1.14 branch creates a wt4 tree, therefore content filtering doesn't work | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
eee2d0b
(Get the code!)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Martin Pool wrote:
> I haven't gone through the reproduction steps but I think what's
> happening is that, because there's no wt in the source, we create the
> default format (or the default for this bzrdir) in the destination
> therefore it doesn't work.
>
> One unattractive workaround is to upgrade the working tree after getting
> it.
>
> It would probably also work to upgrade the hosted branch to 2a; this
> requires everyone be using 1.17 or preferable 1.18rc1.
>
> I think there's still some kind of general bug here in how we choose the
> format; it should probably be determined by the branch and repo.
>
So the issue is that the branch and repository format for 1.9 are
identical to 1.14. The only difference is the WT format. Since there is
no WT, we can't detect that the source is 1.14.
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAkq
b5cAn2lhOmLwStf
=crx1
-----END PGP SIGNATURE-----