All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Barros Pena, Belen" <belen.barros.pena@intel.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
	"webhob@yoctoproject.org" <webhob@yoctoproject.org>
Subject: Re: [Webhob] updating documentation.conf
Date: Thu, 22 Aug 2013 18:11:48 +0100	[thread overview]
Message-ID: <1377191508.6762.28.camel@ted> (raw)
In-Reply-To: <CE3BE9A7.30B64%belen.barros.pena@intel.com>

On Thu, 2013-08-22 at 15:40 +0000, Barros Pena, Belen wrote:
> 
> On 22/08/2013 16:02, "Damian, Alexandru" <alexandru.damian@intel.com>
> wrote:
> 
> >not sure how this should be handled, Paul thinks it should be in there ?
> >
> >
> >AFAIK, suffixed variables get used instead of the normal ones, so they
> >are more like replacements.
> >
> >I guess the design ask that we should the only the variables with doc
> >attached,
> 
> Well Š no :) 
> 
> The design actually asked nothing, since it is still very much in the
> works. My request to the team was in the lines of: can we provide a short
> explanation of the variables we show? When trying to work out how to
> actually do this, we were suggested to use documentation.conf to provide
> such explanations. This is quite different from saying "show variables
> with the [doc] flag".

PREFERRED_PROVIDER is perhaps a special case since it will usually have
a suffix and we're not going to add a [doc] tag for every single one.
Special casing that one in the code may make sense.

Are there any other suffixed variables that are causing similar
problems?

I suspect Paul's proposal of knocking off the lowercase suffixes and
seeing if a [doc] tag exists might be the best/only way to attempt to
handle this.

Cheers,

Richard



  reply	other threads:[~2013-08-22 17:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-14 10:40 [Webhob] updating documentation.conf Barros Pena, Belen
2013-08-16 10:24 ` Richard Purdie
2013-08-21 15:51   ` Barros Pena, Belen
2013-08-22 15:02     ` Damian, Alexandru
2013-08-22 15:26       ` Paul Eggleton
2013-08-22 15:40       ` Barros Pena, Belen
2013-08-22 17:11         ` Richard Purdie [this message]
2013-08-22 17:32           ` Barros Pena, Belen
2013-08-22 20:53             ` Damian, Alexandru
2013-08-22 22:26               ` Richard Purdie
2013-08-23  8:54                 ` Barros Pena, Belen
2013-08-23 14:02                   ` Damian, Alexandru

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=1377191508.6762.28.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=belen.barros.pena@intel.com \
    --cc=paul.eggleton@linux.intel.com \
    --cc=webhob@yoctoproject.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.