All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: bbpetkov@yahoo.de
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] [KERNEL-DOC] kill warnings when building mandocs
Date: Thu, 19 Apr 2007 08:53:36 -0700	[thread overview]
Message-ID: <20070419085336.c029b87c.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20070419062059.GA3974@gollum.tnic>

On Thu, 19 Apr 2007 08:20:59 +0200 Borislav Petkov wrote:

> <snip>
> > > I'm pretty sure the reason you cannot reproduce this warning is the line 
> > > 
> > > <xsl:param name="refentry.version.suppress">1</xsl:param>
> > > 
> > > which can be found in param.xsl, it being a part of the docbook-xsl
> > > distribution. The parameter's name is self-explanatory and a '1' suppresses
> > > the version generation. I was able to get this error because in the
> > > debian docbook-xsl package this param value is set to 0 by default.
> > 
> > Hm, I don't seem to have that file installed (except in
> > /usr/share/xml/docbook/stylesheet/...).  Where would it normally
> > be installed?
> 
> /usr/share/xml/docbook/stylesheet/nwalsh/manpages/param.xsl here

OK, I have that one, with a /current/ stuck in there:


/usr/share/xml/docbook/stylesheet/nwalsh/1.69.1/manpages/param.xsl

<xsl:param name="refentry.version.suppress">0</xsl:param>


> > > This means, some users will get this warning and some will not, depending on the
> > > setting in the param.xsl file. What is the way to go here wrt to a solution
> > > dealing with all cases:
> > > 
> > > 1. patch the kernel-doc?
> > > 2. issue an info so that the user can suppress the annoying warning by
> > > themselves?
> > > 3. ...?
> > 
> > 
> > Are other people seeing these warning messages ??
> Hm, is anyone building the manpages target at all?

Other than the 2 of us... I couldn't say.

> > If so, I think that we should patch the kernel-doc.  I don't think
> > that many people would read info about how to avoid the warnings.


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2007-04-19 15:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-13  9:14 [PATCH] [KERNEL-DOC] kill warnings when building mandocs Borislav Petkov
2007-04-13  9:29 ` Borislav Petkov
2007-04-18 17:16   ` Randy Dunlap
2007-04-19  6:30     ` Borislav Petkov
2007-04-19  7:19       ` [PATCHv2] " Borislav Petkov
2007-04-19 16:21         ` Randy Dunlap
2007-04-20  5:59           ` Borislav Petkov
2007-04-21  7:20         ` Andrew Morton
2007-04-22  7:40           ` [PATCHv3] " Borislav Petkov
2007-04-22  7:49           ` [PATCHv3] [KERNEL-DOC] kill warnings when building mandocs (fixed whitespaces) Borislav Petkov
2007-04-22 15:59             ` [PATCHv4] [KERNEL-DOC] kill warnings when building mandocs (final) Borislav Petkov
2007-04-14 16:13 ` [PATCH] [KERNEL-DOC] kill warnings when building mandocs Randy Dunlap
2007-04-15  7:10   ` Borislav Petkov
2007-04-17 10:49     ` Borislav Petkov
2007-04-18 16:03       ` Randy Dunlap
2007-04-19  6:20         ` Borislav Petkov
2007-04-19 15:53           ` Randy Dunlap [this message]
2007-04-20  6:02             ` Borislav Petkov
2007-04-25 20:22               ` Randy Dunlap
  -- strict thread matches above, loose matches on Subject: below --
2007-04-22 23:04 Randy Dunlap

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=20070419085336.c029b87c.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=bbpetkov@yahoo.de \
    --cc=linux-kernel@vger.kernel.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.