branch nicks are poorly explained

Bug #50466 reported by Wouter van Heyst
Affects Status Importance Assigned to Milestone

Bug Description

I don't explicitly set branch nicks, so I had some trouble trying to explain what they are for to a new user 'feature branches nicely show up in the log' was the best I could think of.

Searching around a bit, we don't seem to explain it in the online help, docs/ or on the wiki.

A bit of #bzr over the course of 10 minutes.

< jvw> right, ok -- btw, I see two branch nicks: dak and debian-archive-kit, what is the practical effect for nicknames, and multiple branches having the same nickname?
< jvw> btw, I googled, but I couldn't find any useful page -- is there some intro on bzr nicknames?
< LarstiQ> jvw: you can explicitly set it, or it will be the basename of the branch root
< spiv> LarstiQ: An introduction would tell you what they're *for*, not how they get set :)
< LarstiQ> spiv: I'm still looking for that ;P
< spiv> Well, not *only* how they get set :)
< jvw> I found how to set them, I was curious about useful *uses* :)

Tags: doc
Revision history for this message
John A Meinel (jameinel) wrote :

In general, they are just a hint that is used when browsing the log (or by gannotate/visualize).
They can be helpful to indicate why a line was changed ('oh, it was changed in the feature-foo branch').
They are mostly just a hint, but we could improve documentation on this point.

Changed in bzr:
importance: Untriaged → Medium
status: Unconfirmed → Confirmed
Jelmer Vernooij (jelmer)
tags: added: doc
Jelmer Vernooij (jelmer)
tags: added: check-for-breezy
Jelmer Vernooij (jelmer)
tags: 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.

Other bug subscribers

Remote bug watches

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