"bzr info": More understandable format strings needed

Bug #248900 reported by Tim Penhey
16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
Confirmed
Medium
Unassigned
Breezy
Triaged
Medium
Unassigned
Launchpad itself
Fix Released
Medium
Unassigned

Bug Description

Branch format: Branch format 6
Repository format: Packs containing knits without subtree support

"Packs containing knits without subtree support" is not too helpful for normal people. "Packs" would be more helpful IMHO.

Not sure what to do about branch formats though.

Revision history for this message
Jonathan Lange (jml) wrote :

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.

Revision history for this message
Tim Penhey (thumper) 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.

Changed in launchpad-bazaar:
importance: Undecided → High
status: New → Triaged
Revision history for this message
Robert Collins (lifeless) wrote : Re: [Bug 248900] Re: More understandable format strings needed

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>.

Revision history for this message
Jonathan Lange (jml) wrote : Re: More understandable format strings needed

Related to bug 264730 and bug 250160.

Revision history for this message
Ian Clatworthy (ian-clatworthy) wrote :

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

Changed in bzr:
importance: Undecided → Medium
status: New → Triaged
Tim Penhey (thumper)
Changed in launchpad-bazaar:
importance: High → Medium
Revision history for this message
Samuel Bronson (naesten) wrote :

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".

summary: - More understandable format strings needed
+ "bzr info": More understandable format strings needed
Revision history for this message
Martin Albisetti (beuno) wrote :

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.

Revision history for this message
Aaron Bentley (abentley) wrote :

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

Revision history for this message
Martin Albisetti (beuno) wrote :

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

Revision history for this message
Samuel Bronson (naesten) wrote :

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.

Revision history for this message
Tim Penhey (thumper) wrote :

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

Changed in launchpad-code:
status: Triaged → Fix Released
Martin Pool (mbp)
Changed in bzr:
status: Triaged → Confirmed
Jelmer Vernooij (jelmer)
tags: added: check-for-breezy
Jelmer Vernooij (jelmer)
tags: added: format-infrastructure info
removed: check-for-breezy
Changed in brz:
status: New → Triaged
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.