"bzr info": More understandable format strings needed

These strings come straight from Bazaar. If we want to fix them, or provide shorter alternatives, then it's probably a good idea to do it there.

Yes and no. We use the strings to identify the Enum value, but we have full control over what we show to the user.

On Wed, 2008-07-16 at 05:54 +0000, Tim Penhey wrote:
> Yes and no. We use the strings to identify the Enum value, but we have
> full control over what we show to the user.

We can still improve the descriptions in the registry to be nicer :)

-Rob
--
GPG key available at: <http://www.robertcollins.net/keys.txt>.

Related to bug 264730 and bug 250160.

The help descriptions for formats have been recently improved. Please retest in 1.11.

The branch format descriptions should be supplemented by bzr-readable names, or at the very least be easy to correlate with "bzr help current-formats" or "bzr help other-formats".

What we should be exposing is "2a", "0.92", etc. It's what we use to talk about formats, and it' what the user needs to use to bzr upgrade --$format.
The current information we're exposing should be downplayed in the UI, since it's really only useful to bzr developers.

There have been plenty of complaints about the short display in "bzr info", which is why we went with displaying the full info here.

This is confusing because it's targeted to both bzr and LP, but I was referring to LP, not bzr :)

Martin: I feel precisely the same way about "bzr info", though! I feel that LP and "bzr info" should both display text that includes the string to pass to "--format" to create something in or convert something to that format.

Since Launchpad is taking the strings directly from Bazaar, I'm going to close the Launchpad task.