From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: Strangeness in generated xen-command-line.html
Date: Wed, 19 Nov 2014 10:37:44 +0000 [thread overview]
Message-ID: <546C72F8.2020704@citrix.com> (raw)
In-Reply-To: <1416393024.29243.20.camel@citrix.com>
On 19/11/14 10:30, Ian Campbell wrote:
> On Wed, 2014-11-19 at 10:24 +0000, Andrew Cooper wrote:
>> On 19/11/14 10:12, Ian Campbell wrote:
>>> http://xenbits.xen.org/docs/unstable/misc/xen-command-line.html has a
>>> bunch of random sha id's in it, where the 4.4-testing version does not.
>>>
>>> They seem to have replaced the various
>>> `= <boolean>`
>>>
>>> Default: `true`
>>>
>>> Bits.
>>>
>>> Andy, Any thoughts or should I investigate?
>>>
>>> I don't see anything since 4.4 touching the html generation itself (we
>>> added pandoc for pdf but didn't touch HTML afaict).
>>>
>>> Ian.
>>>
>> I have looked into it before but didn't get very far. I suspect it
>> might be a bug in wheezy's markdown. It doesn't reproduce when building
>> using other versions of markdown.
> Right.
>
> It seems to be triggered by the line:
> `S` is an integer 1 or 2 for the number of stop bits.
> just removing that makes the issue go away. It's not the `s since
> removing just those retains the issue. WTAF!
>
> Ian.
>
So it does. As best as I can tell, that is all legal mardown for a
nested block.
~Andrew
next prev parent reply other threads:[~2014-11-19 10:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 10:12 Strangeness in generated xen-command-line.html Ian Campbell
2014-11-19 10:21 ` Ian Campbell
2014-11-19 10:24 ` Andrew Cooper
2014-11-19 10:30 ` Ian Campbell
2014-11-19 10:37 ` Andrew Cooper [this message]
2014-11-19 10:38 ` Ian Campbell
2014-11-19 10:46 ` Ian Campbell
2014-11-19 10:52 ` Andrew Cooper
2014-11-19 11:04 ` Ian Campbell
2014-11-19 11:05 ` Andrew Cooper
2014-11-19 11:11 ` Konrad Rzeszutek Wilk
2014-11-20 15:58 ` Ian Campbell
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=546C72F8.2020704@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.