Bug #488
closed"OBSELETE"
100%
Description
There are several occurrences of "obselete" in the man pages and printed strings. They should all read "obsolete" instead.
Also, note the following:
$ lttng disable-consumer -h The disable-consumer command is now obselete. Warning: Some command(s) went wrong
It is exaggerated to report a requested help on an obsolete command as something that "went wrong". The help was obtained as requested by the user: nothing went wrong. No other lttng command -h will be reported as "wrong". Except for lttng enable-consumer -h, that is. :-)
Updated by Daniel U. Thibault over 11 years ago
While on the topic of typos, there are also occurrences of "subbufers" instead of "sub-buffers".
Updated by Anonymous over 11 years ago
Also, as I mentioned a couple weeks back, "obsolete" normally means "the feature is still there, but unsupported, use at your own risk, and expect it to be removed soon" and not "this has been completely removed from the code, but we kept the command-line option just so that hypothetical scripts don't break1". Just saying ;)
[1] protip: those scripts will be broken anyway
Updated by David Goulet over 11 years ago
- Status changed from New to Confirmed
- Assignee set to David Goulet
- Target version set to 2.2
Updated by David Goulet over 11 years ago
- Status changed from Confirmed to Resolved
- % Done changed from 0 to 100
Applied in changeset 9c6bda17fc9edd28c46e52fdf439d37da81e8d9a.