From: Jens Axboe <axboe@suse.de>
To: Aaron Blew <aaron.blew@district6.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bigggg Maxtor drives (fwd)
Date: Thu, 10 Jan 2002 20:14:13 +0100 [thread overview]
Message-ID: <20020110201413.K19814@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.33L.0201101010090.2985-100000@imladris.surriel.com> <1010689195.390.3.camel@workmonkey>
In-Reply-To: <1010689195.390.3.camel@workmonkey>
On Thu, Jan 10 2002, Aaron Blew wrote:
> This is where I am right now :). 25+GB of space I can't use is
> frustrating, especially considering that I've only got 30-40GB free,
> with space dissappearing regularly (I obsessively capture video off TV
I always read emails like that, what exactly is wrong with having
patches out-of-kernel for a while? Surely nothing prevents you from
applying them when you upgrade your kernel?!
Note that this is not an email saying we should not include Andre's
work, I'm quite sure we will do that eventually.
--
Jens Axboe
next prev parent reply other threads:[~2002-01-10 19:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-10 1:46 Bigggg Maxtor drives (fwd) Andre Hedrick
2002-01-10 3:14 ` Benjamin S Carrell
2002-01-10 4:03 ` Chris Ball
2002-01-10 4:31 ` Jim Crilly
2002-01-10 12:11 ` Rik van Riel
2002-01-10 12:15 ` Jens Axboe
2002-01-10 13:22 ` Marcel J.E. Mol
2002-01-10 14:56 ` Hans Reiser
2002-01-10 15:04 ` Jens Axboe
2002-01-10 12:23 ` Lionel Bouton
2002-01-10 12:40 ` Alan Cox
2002-01-10 12:45 ` David Weinehall
2002-01-10 13:47 ` Alan Cox
2002-01-10 18:59 ` Aaron Blew
2002-01-10 19:14 ` Jens Axboe [this message]
2002-01-10 19:14 ` Ricky Beam
2002-01-10 19:59 ` Alan Cox
2002-01-10 19:08 ` Ricky Beam
2002-01-10 4:59 ` Andre Hedrick
2002-01-10 9:50 ` Henning P. Schmiedehausen
2002-01-11 21:13 ` Rogier Wolff
2002-01-12 9:14 ` Andre Hedrick
-- strict thread matches above, loose matches on Subject: below --
2002-01-10 10:00 Andries.Brouwer
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=20020110201413.K19814@suse.de \
--to=axboe@suse.de \
--cc=aaron.blew@district6.org \
--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