From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: Stefan Weil <sw@weilnetz.de>,
Pranith Kumar <bobby.prani@gmail.com>,
QEMU Developer <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] Fix regressions caused by renaming README
Date: Wed, 20 Jul 2016 09:00:06 +0200 [thread overview]
Message-ID: <b36fa309-1f64-69cf-2f25-edff744df77d@redhat.com> (raw)
In-Reply-To: <87fur4izmm.fsf@dusky.pond.sub.org>
On 20/07/2016 08:37, Markus Armbruster wrote:
> I'd less unenthusiastic if MarkDown worked the same everywhere. Its
> common core does, but how would we ensure we stick to the common core?
> How would we even know what the core common to the various MarkDown
> dialects is?
README.md uses exactly three features:
* monospace text
* headings
* lists
> Or are we ready to commit to GitHub's dialect?
We probably want to rely on GitHub's stricter interpretation of
underscores, where they only start/end italic formatting if they are
respectively the first or the last character in the word. This is a
common extension (for example Stack Exchange does the same).
The question is: is anyone actually viewing formatted markdown anywhere
else than on github?
Paolo
next prev parent reply other threads:[~2016-07-20 7:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 17:47 [Qemu-devel] [PATCH] Fix regressions caused by renaming README Stefan Weil
2016-07-19 18:15 ` Pranith Kumar
2016-07-19 20:53 ` Peter Maydell
2016-07-19 21:17 ` Pranith Kumar
2016-07-19 21:33 ` Peter Maydell
2016-07-20 6:37 ` Markus Armbruster
2016-07-20 7:00 ` Paolo Bonzini [this message]
2016-07-20 7:07 ` Fam Zheng
2016-07-20 7:09 ` Paolo Bonzini
2016-07-20 7:18 ` Fam Zheng
2016-07-20 8:47 ` Daniel P. Berrange
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=b36fa309-1f64-69cf-2f25-edff744df77d@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=bobby.prani@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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).