From: Roman Zippel <zippel@linux-m68k.org>
To: Russell King <rmk@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Up silly limit on .config line length
Date: Wed, 6 Nov 2002 14:32:30 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.44.0211061425280.6949-100000@serv> (raw)
In-Reply-To: <20021105233844.J24606@flint.arm.linux.org.uk>
Hi,
On Tue, 5 Nov 2002, Russell King wrote:
> I believe that this arbitary limit should be eliminated by some method.
> However, as a "get you working" patch with a new arbitary limit of 1024
> characters:
I was already wondering, how much I should allow. :)
But I'd rather set an arbitrary limit (and warn) than allowing an
arbitrary long string.
bye, Roman
next prev parent reply other threads:[~2002-11-06 13:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-05 23:38 Russell King
2002-11-06 13:32 ` Roman Zippel [this message]
2002-11-06 13:34 ` Russell King
2002-11-06 21:32 ` Sam Ravnborg
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.0211061425280.6949-100000@serv \
--to=zippel@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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®