public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Masanari Iida <standby24x7@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	lunar@debian.org
Subject: Re: make htmldocs on linux-next failed with warnings.
Date: Thu, 6 Aug 2015 12:43:31 -0600	[thread overview]
Message-ID: <20150806124331.10016ae7@lwn.net> (raw)
In-Reply-To: <20150716083159.4ba785d9@lwn.net>

On Thu, 16 Jul 2015 08:31:59 -0600
Jonathan Corbet <corbet@lwn.net> wrote:

> On Thu, 16 Jul 2015 15:28:56 +0100
> Ben Hutchings <ben@decadent.org.uk> wrote:
> 
> > On Thu, 2015-07-16 at 23:22 +0900, Masanari Iida wrote:  
> > > make htmldocs on linux-next have some parser warnings.
> > > Following commit cause the warning.    
> > 
> > Yes it has warnings but they should be non-fatal.  
> 
> Even so, we don't really want to be adding warnings to the build.
> Hopefully it shouldn't be too hard to fix these...?

So I've not heard any further on this.  I think at this point I'm going
to revert the patch in question; adding warnings for everybody is just
not the right thing to do.  The other patches in the series can stay.

Having spent some time pondering on the issue, I've also concluded that
this isn't quite the right solution to the problem.  Better, I think, to
have docproc filter out the duplicates directly, and to direct the output
to a different file type (.fxml, say).  Otherwise the .xml files can have
two different things depending on which type of docs was built first,
leading possibly to other formats being built with missing stuff.

I may hack together a solution along these lines, just because I do think
that the reproducible builds goal is an important one.  But I've got a
*bunch* of other stuff that I have to get done, so I'm not quite sure
when I can get to it.

jon

  reply	other threads:[~2015-08-06 18:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-16 14:22 make htmldocs on linux-next failed with warnings Masanari Iida
2015-07-16 14:28 ` Ben Hutchings
2015-07-16 14:31   ` Jonathan Corbet
2015-08-06 18:43     ` Jonathan Corbet [this message]
2015-08-06 22:39       ` Ben Hutchings

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=20150806124331.10016ae7@lwn.net \
    --to=corbet@lwn.net \
    --cc=ben@decadent.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lunar@debian.org \
    --cc=standby24x7@gmail.com \
    /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