From: ebiederm+eric@ccr.net (Eric W. Biederman)
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.rutgers.edu, linux-mm@kvack.org,
MOLNAR Ingo <mingo@chiara.csoma.elte.hu>
Subject: Re: [PATCHES]
Date: 23 May 1999 09:54:53 -0500 [thread overview]
Message-ID: <m1k8tzsuo1.fsf@flinx.ccr.net> (raw)
In-Reply-To: Linus Torvalds's message of "Sat, 22 May 1999 23:03:00 -0700 (PDT)"
>>>>> "LT" == Linus Torvalds <torvalds@transmeta.com> writes:
LT> On 22 May 1999, Eric W. Biederman wrote:
>>
>> I've been busy working to improve the basic mechanisms of the
>> page cache, and finally what appears to be a stable set of patches, with
>> no hacks against 2.3.3
LT> I have three worries:
LT> - this is large, with no input from anybody else that I have seen.
Not much. I had aggreements in principal but no one else has looked at it
real hard.
LT> - I absolutely detest getting encoded patches. It makes it much harder
LT> for me to just quickly look them over for an immediate feel for what
LT> they look like.
O.k. I do that for large patches because I'm paranoid about the mailers
in between. . .
LT> - Ingo just did the page cache / buffer cache dirty stuff, this is going
LT> to clash quite badly with his changes I suspect.
Interesting. I have been telling folks I've been working on this for quite
a while. I wish I'd heard about him or vis versa.
Ingo can I get a pointer to your work?
Linus, I'll be resending the patches later today (church is in about 5 minutes).
LT> The other worries I'll see about later. The short descriptions sound fine,
Cool. If you agree with my work in principal, that makes life easier.
Now I just need to worry about the details of my patches.
Eric
--
To unsubscribe, send a message with 'unsubscribe linux-mm my@address'
in the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
next prev parent reply other threads:[~1999-05-23 14:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-23 3:36 [PATCHES] Eric W. Biederman
1999-05-23 6:03 ` [PATCHES] Linus Torvalds
1999-05-23 14:54 ` Eric W. Biederman [this message]
1999-05-23 15:49 ` [PATCHES] Ingo Molnar
1999-05-23 18:34 ` [PATCHES] Eric W. Biederman
1999-05-27 6:24 ` [PATCHES] Stephen C. Tweedie
1999-05-27 19:55 ` [PATCHES] Chuck Lever
1999-05-27 23:39 ` [PATCHES] Stephen C. Tweedie
1999-05-28 5:30 ` [PATCHES] Chuck Lever
1999-05-29 1:24 ` [PATCHES] Stephen C. Tweedie
1999-05-30 17:01 ` [PATCHES] Eric W. Biederman
1999-05-27 6:25 ` [PATCHES] Stephen C. Tweedie
1999-05-24 17:20 ` [PATCHES] Manfred Spraul
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=m1k8tzsuo1.fsf@flinx.ccr.net \
--to=ebiederm+eric@ccr.net \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=mingo@chiara.csoma.elte.hu \
--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 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.