Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DD9FB10FEB for ; Thu, 22 Aug 2013 04:46:45 +0000 (UTC) Received: (qmail 825 invoked by uid 500); 22 Aug 2013 04:46:45 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 520 invoked by uid 500); 22 Aug 2013 04:46:39 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 512 invoked by uid 99); 22 Aug 2013 04:46:38 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Aug 2013 04:46:38 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of shadowsor@gmail.com designates 209.85.215.50 as permitted sender) Received: from [209.85.215.50] (HELO mail-la0-f50.google.com) (209.85.215.50) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Aug 2013 04:46:33 +0000 Received: by mail-la0-f50.google.com with SMTP id ek20so1019129lab.37 for ; Wed, 21 Aug 2013 21:46:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=qe7lEku1D4uX2plyWo1eTxLRw5uT5VSYCSpubSRfMbM=; b=kx2I7n23Oo7v/bf672hA9bwcRY7j34LUIFMZrB+eZ2xxn8Kg+wjblGaBY1Jb4JPqOD 8h1EZkcjTFmFOBmKx4frC9TYQGrUVqUdKT6uFKXdGGlll8H+fNIfy/BURcjrYDbChD0q zdaMUdNsGkZ4GiQ37YG6vlv0oWh3abI+7O/lryTbpA+mr0maN0IaA9ujYT+stTP3ybow vRWvYq8PaHGpxLfd2DujPDXwjGsx0fKCA5QIYtqrs+aNm2ddBv9tLB8Fwur2TPlMoqTt 01EfSlwaM4ni77bnHvTujOnQ6sGkfbfDPinS1pGR6g+g1T+im/r/NfUC3/q6tb6+hgLc yR2g== MIME-Version: 1.0 X-Received: by 10.112.64.36 with SMTP id l4mr9889440lbs.15.1377146771807; Wed, 21 Aug 2013 21:46:11 -0700 (PDT) Received: by 10.114.70.242 with HTTP; Wed, 21 Aug 2013 21:46:11 -0700 (PDT) Received: by 10.114.70.242 with HTTP; Wed, 21 Aug 2013 21:46:11 -0700 (PDT) Date: Wed, 21 Aug 2013 22:46:11 -0600 Message-ID: Subject: Api doc categories From: Marcus Sorensen To: dev@cloudstack.apache.org Content-Type: multipart/alternative; boundary=001a11c3eee423332504e481f867 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c3eee423332504e481f867 Content-Type: text/plain; charset=ISO-8859-1 I've spent a few minutes trying to figure out how API commands are linked with their categories in the API documentation. I read the doc about annotations and generating the docs. I see the known_categories in gen_toc.py, but I don't see any place in the annotations where one might define a specific command under a specific category. When I build I do see it complain about uncategorized commands, such as the ones in the netapp plugin (or whatever provides the 'filer' commands). --001a11c3eee423332504e481f867--