On Wed, Sep 21, 2011 at 12:34 PM, Thomas Kahle <to...@gentoo.org> wrote: > Let's have a page in our docs where everybody can explain his or her > tool. Where in the hierarchy should the page be? How about: > http://www.gentoo.org/proj/en/base/arch-testing
Please! And the documentation should include examples of common workflows, not just a dump of command line options and what they do. Let's start with the use case of I have a stablereq for a package and I want to test it. Just tell me how to do it, and don't make me figure out which combination of options works best. Oh, and make sure the instructions include any necessary cleanup if the process leaves cruft in package.keywords/etc. Rich