From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: Strangeness in generated xen-command-line.html
Date: Wed, 19 Nov 2014 10:38:44 +0000
Message-ID: <1416393524.29243.21.camel@citrix.com>
References: <1416391975.29243.16.camel@citrix.com>
	<546C6FEB.8010308@citrix.com> <1416393024.29243.20.camel@citrix.com>
	<546C72F8.2020704@citrix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <546C72F8.2020704@citrix.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen-devel <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

On Wed, 2014-11-19 at 10:37 +0000, Andrew Cooper wrote:
> 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.

Removing the preceeding nested list also "fixes" it, so I suspect some
sort of error in handling nested lists with surrounding text in the
parent entry, or something. I've not been able to find a workaround...

> 
> ~Andrew