bzr global options should be added to man page

There should be documented in bzr help standard-options.

They aren't yet.

The bug was raised for bzr version 1.12.1 on 2009-02-28, so it is now out-dated and should be disposed off by changing the Status to Solved.

OldAl, simple duration does not solve a bug. This bug is still present (I just checked). If you are working on fixing it, please reassign it to yourself and set the status to In progress (as per our process documentation).

@Robert - which version of bzr are you using? I agree with that simple duration is no substitute to eliminating the bug. But the question of version is vital, as between 1.12 and 2.x is a huge leap for all x, Would appreciate the information of the bzr version used to verify the state.

On Sun, 2009-11-29 at 07:10 +0000, OldAl wrote:
> @Robert - which version of bzr are you using? I agree with that simple
> duration is no substitute to eliminating the bug. But the question of
> version is vital, as between 1.12 and 2.x is a huge leap for all x,
> Would appreciate the information of the bzr version used to verify the
> state.

I checked in trunk.

I love that you want to help. Please be sure to _check_ that bugs are
fixed, not speculate about it though: as a new contributor to the
project you don't have the historical context to make accurate guesses
yet - that will come with time.

BTW, 1.12 -> 2.0.0 is only 7 months apart, not really that big a
distance.

-Rob

--no-plugins, --builtin and --no-aliases are documented under 'bzr help global-options'.

'bzr help standard-options' lists --help, --verbose and --quiet, but notes that these are different from global options since they can be used in aliases.

So, is this bug closed/invalid; or should parts of global-options be moved to standard-options; or should the man page be changed? The man page currently refers the user to 'bzr help'.

The remark on aliases in 'standard-options' implies that global options --concurrency, --lsprof, etc., cannot be used with aliases; is this correct?