Comment 4 for bug 748141

On Mon, 2011-04-04 at 17:57 +0000, Eli Zaretskii wrote:
> I see your point about adding confusion for new users, and I agree.
>
> However, please note that commands are not just for new users. Veteran
> users that are not bzr developers are also worthy of being catered to by
> bzr...
>
> Also, when you say these commands are fo debugging, you probably mean
> that this is how they cam into existence. While that is probably true,
> I would argue that once they do exist, their fate should be decided by
> their utility for mere mortals, not by the historical curiosities.
It's unrelated to their origin. These commands are only really useful
during debugging - e.g. when trying to find out why a file wasn't
merged, or why a merge went wrong. Normal users shouldn't have to bother
with e.g. file ids. Perhaps diagnostics is a better term?

Independent of how to call them, I'm not sure these commands should be
visible in "bzr help commands". Perhaps we should consider other ways to
make the "bzr help commands" list smaller, e.g. categorizing the
commands.

Cheers,

Jelmer