From: Stefan Weil <sw@weilnetz.de>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/5] docs: convert specifications to markdown
Date: Tue, 15 Nov 2011 07:07:12 +0100 [thread overview]
Message-ID: <4EC20190.2020001@weilnetz.de> (raw)
In-Reply-To: <1321310505-27845-1-git-send-email-aliguori@us.ibm.com>
Am 14.11.2011 23:41, schrieb Anthony Liguori:
> Right now our specs are written in psuedo-wiki syntax. This series converts
> them to markdown. markdown is a simple markup format that's gaining in
> popularity.
>
> The big advantage of using markdown is that there are tools that can convert it
> to relatively simple HTML. That means we can build a make infrastructure that
> generates a nice set of static web pages.
>
> The syntax is also more human friendly than mediawiki syntax.
>
> To see what the stylized version of this looks like, check out:
>
> https://github.com/aliguori/qemu/tree/markdown/docs/specs
Maybe the file names could also be cleaned: either remove _spec
as it is not needed (or do you add _src to source file names),
or add it to all file names.
Regards,
Stefan Weil
next prev parent reply other threads:[~2011-11-15 6:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 22:41 [Qemu-devel] [PATCH 0/5] docs: convert specifications to markdown Anthony Liguori
2011-11-14 22:41 ` [Qemu-devel] [PATCH 1/5] docs: convert qed_spec.txt " Anthony Liguori
2011-11-14 22:41 ` [Qemu-devel] [PATCH 2/5] docs: convert qcow2 specification " Anthony Liguori
2011-11-14 22:41 ` [Qemu-devel] [PATCH 3/5] docs: convert ivshmem device spec " Anthony Liguori
2011-11-14 22:41 ` [Qemu-devel] [PATCH 4/5] docs: convert acpi_pci_hotplug " Anthony Liguori
2011-11-14 22:41 ` [Qemu-devel] [PATCH 5/5] docs: add readme to specifications directory Anthony Liguori
2011-11-15 6:07 ` Stefan Weil [this message]
2011-11-15 8:28 ` [Qemu-devel] [PATCH 0/5] docs: convert specifications to markdown Avi Kivity
2011-11-15 13:44 ` Anthony Liguori
2011-11-15 13:51 ` Avi Kivity
2011-11-15 13:56 ` Alex Bradbury
2011-11-15 17:25 ` Stefano Stabellini
2011-11-15 14:49 ` Anthony Liguori
2011-11-15 18:06 ` Stefan Weil
2011-11-15 19:00 ` 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=4EC20190.2020001@weilnetz.de \
--to=sw@weilnetz.de \
--cc=aliguori@us.ibm.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).