qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Amit Shah <amit.shah@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu list <qemu-devel@nongnu.org>, Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH REBASE/RESEND 0/4] Auto-document qdev devices
Date: Thu, 17 Feb 2011 19:15:39 +0530	[thread overview]
Message-ID: <20110217130944.GE27487@amit-x200.redhat.com> (raw)
In-Reply-To: <4D5AA5E7.40203@codemonkey.ws>

On (Tue) 15 Feb 2011 [10:12:23], Anthony Liguori wrote:
> On 02/04/2011 12:18 AM, Amit Shah wrote:
> >Hello,
> >
> >This is yet another rebase of the patchset I'd sent earlier.
> >
> >The usual notes apply: this is just the start, just getting the
> >framework in place and a few examples so that people can then pick up
> >and start documenting their devices and options.  We want to see all
> >of the devices covered, and hopefully turn on build_bug_on() on an
> >empty doc string.
> >
> >Maintainers should perhaps also look for patches that introduce
> >options without documentation.
> >
> >That's the long-term goal (0.15-final).  For short-term, I'll be
> >preparing follow-on patches that add doc strings for a few more
> >options and perhaps bug people based on git history as to what
> >documentation is to be added for some options.  Also to incorporate
> >Markus's comments on beautifying output.
> >
> >The earlier this patchset goes in the better since it'll reduce
> >conflicts and rebases needed.
> >
> >If this looks acceptable, please apply!
> 
> I think we need to approach this in such a way that we generate not
> only inline documentation but out of line documentation.
> 
> We need a way to extract the docs into a file.  That could mean
> having something like a .hx file or just doing some clever things
> with grep DEFINE_PROP.

An external tool that uses grep, sed and awk will work just fine to
export all of this to some wiki page or anywhere else desirable.


		Amit

  reply	other threads:[~2011-02-17 13:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-04  6:18 [Qemu-devel] [PATCH REBASE/RESEND 0/4] Auto-document qdev devices Amit Shah
2011-02-04  6:18 ` [Qemu-devel] [PATCH REBASE/RESEND 1/4] qdev: Add a description field for qdev properties for documentation Amit Shah
2011-02-15 16:43   ` Anthony Liguori
2011-02-17 13:06     ` Amit Shah
2011-02-17 13:12       ` Anthony Liguori
2011-02-17 13:37         ` Amit Shah
2011-02-18  8:59         ` Markus Armbruster
2011-02-18 15:21           ` Anthony Liguori
2011-02-18  8:54     ` Markus Armbruster
2011-02-04  6:18 ` [Qemu-devel] [PATCH REBASE/RESEND 2/4] virtio-serial: Add description fields for qdev properties Amit Shah
2011-02-15 16:10   ` Anthony Liguori
2011-02-17 13:03     ` Amit Shah
2011-02-17 13:11       ` Anthony Liguori
2011-02-17 13:39         ` Amit Shah
2011-02-04  6:18 ` [Qemu-devel] [PATCH REBASE/RESEND 3/4] net.h: Add description fields for qdev properites Amit Shah
2011-02-04  6:18 ` [Qemu-devel] [PATCH REBASE/RESEND 4/4] block_int.h: Provide documentation for common block qdev properties Amit Shah
2011-02-04  8:02 ` [Qemu-devel] [PATCH REBASE/RESEND 0/4] Auto-document qdev devices Markus Armbruster
2011-02-15 16:12 ` Anthony Liguori
2011-02-17 13:45   ` Amit Shah [this message]
2011-02-18  8:53   ` Markus Armbruster
2011-02-18 15:18     ` Anthony Liguori

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110217130944.GE27487@amit-x200.redhat.com \
    --to=amit.shah@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=armbru@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).