From: Adrian Bunk <bunk@fs.tum.de>
To: Jan-Hinnerk Reichert <jan-hinnerk_reichert@hamburg.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.4.22-pre1] menuconfig oddity
Date: Sun, 29 Jun 2003 21:05:55 +0200 [thread overview]
Message-ID: <20030629190555.GC282@fs.tum.de> (raw)
In-Reply-To: <200306291237.23250.jan-hinnerk_reichert@hamburg.de>
On Sun, Jun 29, 2003 at 12:37:23PM +0200, Jan-Hinnerk Reichert wrote:
>...
> > If this isn't the problem, please send your .config.
>
> Unfortunately, I haven't saved the non-working .config.
>
> Which config should I sent? The old 2.4.20-SuSE, the one after "make
> oldconfig"?
The only .config that would help is a non-working .config.
Please try to reproduce the problem.
> Jan-Hinnerk
TIA
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2003-06-29 18:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-23 17:27 [2.4.22-pre1] menuconfig oddity Jan-Hinnerk Reichert
2003-06-26 17:50 ` Adrian Bunk
2003-06-29 10:37 ` Jan-Hinnerk Reichert
2003-06-29 19:05 ` Adrian Bunk [this message]
2003-06-29 20:02 ` Jan-Hinnerk Reichert
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=20030629190555.GC282@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=jan-hinnerk_reichert@hamburg.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.