Project | Branch | Lines +/- | Subject | |
---|---|---|---|---|
operations/software/tools-webservice | master | +201 -0 | Man page for webservice |
Details
Related Objects
- Mentioned In
- T190696: [Gsoc 2018] Proposal for Toolforge webservice command Improvement
T190638: GSoC 2018 proposal for Improvements for the Toolforge 'webservice' command
T177603: Proposal: Improvements for the Toolforge 'webservice' command
T175768: Improvements for the Toolforge 'webservice' command
Event Timeline
We should / can kill webservice from the repo now, it isn't used anywhere (webservice2 is the default webservice now).
We can just put help files in --help there maybe?
I know, but I want to put webservice{,2} back in the repository. IIRC you pulled it out of there to hot-fix some issues, and now that these have been worked out and after you'll build in the bigbrother replacement, there's no longer a need to pass on tests & Co. (or need +2 from ops). When I review changes, I have a hard time figuring out the semantics of the different options and how they are affected, and I want my laziness back and let Jenkins do the work :-).
Debian's policy for man pages is AFAICS not that they should be there only for executables installed from a package, but that for each command, a user can find a manual by typing man command. So in theory, I would jot down a man page for executables installed by Puppet as well, but with no linter nagging in the past it was easier to just explain how portgrabber works when a user asked for the man page.
Change 437054 had a related patch set uploaded (by Nehajha; owner: Nehajha):
[operations/software/tools-webservice@master] Man page for webservice
Change 437054 abandoned by BryanDavis:
[operations/software/tools-webservice@master] Man page for webservice
Reason: