From: Robert Love <rml@novell.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] inotify 0.9
Date: Mon, 20 Sep 2004 20:02:28 -0400 [thread overview]
Message-ID: <1095724948.2454.17.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.3.96.1040920180744.11755B-100000@gatekeeper.tmr.com>
On Mon, 2004-09-20 at 18:59 -0400, Bill Davidsen wrote:
> I'm sorry you think think I'm talking to hear myself talk, the
> point I'm making is valid to me.
Judgment suggests I should drop this, but the problem is that you never
made a valid or well-informed point.
You started off with "Did you work for Microsoft?" and you followed up
with questions and critiques demonstrating no understanding whosoever
for the way that Linux dcache or inode management works and further that
you did not even read the patch.
My reply "well dnotify has this same issue" is not a rallying behind the
status quo (I mean, I want dnotify dead myself) but that no one
complains about the size issue with dnotify. John and I want to address
the issues with dnotify.
If we can do something about space consumption, and if it turns out to
be an issue, I am all for it. I do not yet see a way around it, and no
one has shown that normal use in the real world suffers from any issue.
Thanks,
Robert Love
next prev parent reply other threads:[~2004-09-21 0:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 15:52 [RFC][PATCH] inotify 0.9 John McCutchan
2004-09-15 18:00 ` Robert Love
2004-09-16 15:07 ` Bill Davidsen
2004-09-16 16:27 ` Chris Friesen
2004-09-16 22:48 ` Bill Davidsen
2004-09-16 16:39 ` Robert Love
2004-09-20 20:16 ` Bill Davidsen
2004-09-20 21:05 ` Robert Love
2004-09-20 22:59 ` Bill Davidsen
2004-09-21 0:02 ` Robert Love [this message]
2004-09-16 16:46 ` Jan Kara
2004-09-16 22:34 ` Bill Davidsen
2004-09-16 22:57 ` David Lang
2004-09-16 23:22 ` Robert Love
2004-09-16 23:35 ` Alan Cox
2004-09-17 2:29 ` Robert Love
2004-09-17 3:08 ` Nicholas Miell
2004-09-17 14:39 ` Alan Cox
2004-09-17 15:48 ` Robert Love
2004-09-17 14:51 ` Alan Cox
2004-09-17 15:55 ` Robert Love
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=1095724948.2454.17.camel@localhost \
--to=rml@novell.com \
--cc=davidsen@tmr.com \
--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