Christian Hudon wrote:
> Given that a lot of people will be running "bzr upgrade" in the coming
> few months with the release of 2.0 and the official blessing of the new
> "2a" format, here is the still rather unenlightening error message one
> gets when trying to upgrade for format "2a" a repository that is already
> in that format:
>
> bzr: ERROR: The branch format Meta directory format 1 is already at the
> most recent format.
>
> Can I suggest that it might be a good time to fix this buglet and
> include the fix in a 2.0.1 release, as part of "Bazaar 2.0 polishing"
> work? The error message should really talk to the user in the language
> they used to call bazaar. In that particular case, that message should
> really have the string "2a" somewhere in it.
>
I think it is perfectly reasonable to land those sort of fixes into the
2.0.x series.
We just need someone to do it, and to have it take priority over the
other 20 things we are doing. :) (I'm currently on my 3rd or 4th
recursion of X taking precedence over Y that I'd rather be working on,
so my plate is full.)
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Christian Hudon wrote:
> Given that a lot of people will be running "bzr upgrade" in the coming
> few months with the release of 2.0 and the official blessing of the new
> "2a" format, here is the still rather unenlightening error message one
> gets when trying to upgrade for format "2a" a repository that is already
> in that format:
>
> bzr: ERROR: The branch format Meta directory format 1 is already at the
> most recent format.
>
> Can I suggest that it might be a good time to fix this buglet and
> include the fix in a 2.0.1 release, as part of "Bazaar 2.0 polishing"
> work? The error message should really talk to the user in the language
> they used to call bazaar. In that particular case, that message should
> really have the string "2a" somewhere in it.
>
I think it is perfectly reasonable to land those sort of fixes into the
2.0.x series.
We just need someone to do it, and to have it take priority over the
other 20 things we are doing. :) (I'm currently on my 3rd or 4th
recursion of X taking precedence over Y that I'd rather be working on,
so my plate is full.)
John enigmail. mozdev. org/
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAkq 84MYACgkQJdeBCY SNAAP3VQCfQHzWx 0zZsBpIKeX+ IMDFTyea UoMXlao2sbVfEgR +8
MgMAn07ncQHEorV
=Pw9s
-----END PGP SIGNATURE-----