linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org>
To: "Frederick, Fabian" <Fabian.Frederick@prov-liege.be>
Cc: linux-kernel@vger.kernel.org
Subject: RE: [PATCH 1/6] [DVB] Kconfig and Makefile updates
Date: Tue, 29 Jul 2003 12:16:38 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0307291215100.714-100000@serv> (raw)
In-Reply-To: <D9B4591FDBACD411B01E00508BB33C1B01BF88A1@mesadm.epl.prov-liege.be>

Hi,

On Tue, 29 Jul 2003, Frederick, Fabian wrote:

> 	Does \t a standard for menu entries definition ?

No.

> I keep seeing
> multiple spaces in some places which can be troublesome to kernelServer for
> instance.

You really shouldn't parse the Kconfig files yourself, use the library for 
this.

bye, Roman


  reply	other threads:[~2003-07-29 10:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-29 10:05 [PATCH 1/6] [DVB] Kconfig and Makefile updates Frederick, Fabian
2003-07-29 10:16 ` Roman Zippel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-29  9:30 Michael Hunold
2003-07-29  9:58 ` Roman Zippel
2003-07-29 10:02   ` Michael Hunold

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=Pine.LNX.4.44.0307291215100.714-100000@serv \
    --to=zippel@linux-m68k.org \
    --cc=Fabian.Frederick@prov-liege.be \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).