mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stewart Smith <stewart@linux.org.au>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: trivial@rustcorp.com.au, linux-kernel@vger.kernel.org
Subject: Re: [trivial 2.5] kconfig language doc r.e. --help--
Date: Wed, 25 Jun 2003 21:25:34 +1000	[thread overview]
Message-ID: <20030625112534.GB9295@cancer> (raw)
In-Reply-To: <Pine.LNX.4.44.0306251246240.11817-100000@serv>

On Wed, Jun 25, 2003 at 12:48:43PM +0200, Roman Zippel wrote:
> Where did you find the '--help--' version? I'm actually suprised that 
> works. The official alternative is only '---help---'.

I'd *swear* i saw '--help--' yesterday. I'd swear until i was a
light shade of blue....  

Oh well, patch that only references "---help---" below.


--- linux-2.5.73/Documentation/kbuild/kconfig-language.txt	2003-06-15 17:47:18.000000000 +1000
+++ linux-2.5.73-stew1/Documentation/kbuild/kconfig-language.txt	2003-06-25 21:24:28.000000000 +1000
@@ -105,10 +105,13 @@
   or equal to the first symbol and smaller than or equal to the second
   symbol.
 
-- help text: "help"
+- help text: "help" or "---help---"
   This defines a help text. The end of the help text is determined by
   the indentation level, this means it ends at the first line which has
   a smaller indentation than the first line of the help text.
+  "---help---" and "help" do not differ in behaviour, "---help---" is
+  used to help visually seperate configuration logic from help within
+  the file as an aid to developers.
 
 
 Menu dependencies


-- 
Stewart Smith
Vice President, Linux Australia
http://www.linux.org.au (personal: http://www.flamingspork.com)

  reply	other threads:[~2003-06-25 11:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-25  8:43 Stewart Smith
2003-06-25 10:48 ` Roman Zippel
2003-06-25 11:25   ` Stewart Smith [this message]
2003-06-25 12:44     ` Roman Zippel

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=20030625112534.GB9295@cancer \
    --to=stewart@linux.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trivial@rustcorp.com.au \
    --cc=zippel@linux-m68k.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®