[jira] [Assigned] (SVN-4828) svn help: hide experimental, deprecated, and global commands and options

"Julian Foad (Jira)" <[email protected]>
Newsgroups gmane.comp.version-control.subversion.issues
Message-ID <[email protected]>
     [ https://issues.apache.org/jira/browse/SVN-4828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Foad reassigned SVN-4828:
--------------------------------

    Assignee: Julian Foad

> svn help: hide experimental, deprecated, and global commands and options
> ------------------------------------------------------------------------
>
>                 Key: SVN-4828
>                 URL: https://issues.apache.org/jira/browse/SVN-4828
>             Project: Subversion
>          Issue Type: Improvement
>          Components: cmdline client
>    Affects Versions: trunk
>            Reporter: Julian Foad
>            Assignee: Julian Foad
>            Priority: Major
>
> Hide experimental features, by default:
>  - let 'svn help' omit experimental commands and options
>  - let 'svn help -v' include them
> The idea is that users wanting a stable experience should not be distracted by experimental features unless they choose to see them.
> Further, I have been thinking for years we should hide by default:
> - deprecated commands and options
>  - the "Global Options" section of "svn help <subcommand>"
> The global options are sometimes useful, but really only for power users; take up the last half a screenful of output; are shown even for commands where they are irrelevant (all commands accept them but not all use them).
> There are only a few deprecated options, so not such a big distraction, but users don't need to see or learn or care about them at all, except in the most extreme cases like debugging an old script that uses them.
> I plan to hide these three categories by default.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.