From: Aaron Lehmann <aaronl@vitelus.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux v2.5.45
Date: Wed, 30 Oct 2002 17:34:36 -0800 [thread overview]
Message-ID: <20021031013436.GG23438@vitelus.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0210301651120.6719-100000@penguin.transmeta.com>
On Wed, Oct 30, 2002 at 04:56:29PM -0800, Linus Torvalds wrote:
>
>
> Big changes, lots of merges. A number of the merges are fairly
> substantial too.
>
> Device mapper (LVM2), crypto/ipsec stuff for networking, epoll and giving
> the new kernel configurator a chance. Big things.
Now running 'make oldconfig' or 'make menuconfig' requires a Qt
installation. I believe that this is a bug because these still work
fine without Qt when the -k flag is passed to make.
next prev parent reply other threads:[~2002-10-31 1:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 0:56 Linux v2.5.45 Linus Torvalds
2002-10-31 1:22 ` Udo A. Steinberg
2002-10-31 2:40 ` Neil Brown
2002-10-31 1:34 ` Aaron Lehmann [this message]
2002-10-31 1:44 ` Alexander Viro
2002-10-31 1:56 ` Jan Harkes
2002-10-31 9:36 ` [PATCH] check QT only if needed Roman Zippel
2002-10-31 1:37 ` Linux v2.5.45 Adam Huffman
2002-10-31 1:49 ` Jeff Garzik
2002-10-31 8:58 ` Paul
2002-10-31 9:59 ` Joe Thornber
2002-10-31 2:56 ` Martin J. Bligh
2002-10-31 3:31 ` Greg KH
2002-10-31 3:03 ` Udo A. Steinberg
2002-10-31 10:40 ` Jochen Friedrich
2002-10-31 11:21 ` Jochen Friedrich
2002-10-31 11:18 ` Adrian Bunk
2002-11-01 10:29 ` Linux v2.5.45 ipmr.c compile failure Helge Hafting
2002-11-01 23:35 ` Randy.Dunlap
2002-11-02 1:13 ` various 2.5.45 compile problems (intermezzo, pmtu, afs, qt) (was: Linux v2.5.45 ipmr.c compile failure) Bernd Eckenfels
2002-11-01 11:29 ` Linux v2.5.45 Adrian Bunk
2002-11-01 12:58 ` Adrian Bunk
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=20021031013436.GG23438@vitelus.com \
--to=aaronl@vitelus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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