Comment 2 for bug 748141

Revision history for this message
Eli Zaretskii (eliz) 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.

Now for the specific points you made.

Commands slated for deletion of course don't need to be documented.

Merging this hidden functionality with existing non-hidden commands is also an okay solution.

lookup-revision and revision-info are handy for showing revision-id given a revno and vice versa. I don't see how "revno" or "version-info" can help here, except for the current tip revision. Am I missing something?

Likewise for find-merge-base and file-id: what other commands can show this information? I agree that this info is probably needed only rarely, but what's wrong with advertising rarely used commands?