mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Davide Libenzi <davidel@xmailserver.org>
To: John McCutchan <ttb@tentacle.dhs.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC/PATCH] inotify -- a dnotify replacement
Date: Mon, 10 May 2004 15:52:58 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0405101548230.1156@bigblue.dev.mdolabs.com> (raw)
In-Reply-To: <1084228900.28903.2.camel@vertex>

On Mon, 10 May 2004, John McCutchan wrote:

> On Mon, 2004-05-10 at 18:31, Davide Libenzi wrote:
> > On Mon, 10 May 2004, John McCutchan wrote:
> > 
> > > > 3) dnotify cannot easily watch changes for a directory hierarchy
> > > 
> > > People don't seem to really care about this one. Alexander Larsson has
> > > said he doesn't care about it. It might be nice to add in the future.
> > 
> > Please excuse my ignorance, but who is Alexander Larsson? A dnotify 
> > replacement that does not have the ability to watch for a hierarchy is 
> > pretty much useless. Or do you want to drop thousands of single watches to 
> > accomplish that?
> 
> Alexander Larsson is the maintainer of nautilus, gnome-vfs and I think
> the dnotify patch for fam. He made a post to l-k a month or two ago
> about why he doesn't care about it. I do plan on adding this feature in
> the near future though.

GUIs have different requirements. They display a finite number of views on 
directories, so for them it is fine to not have hierarchy watching 
capabilities. A sane dnotify API should have the ability to watch hierarchies.
And it should not even be that much hard to do, since you can just 
backtrace the the point where the change happened to see if there are 
watchers on the parent directories.



- Davide


  reply	other threads:[~2004-05-10 22:55 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-10  1:35 John McCutchan
2004-05-10  2:11 ` Chris Wedgwood
2004-05-10 22:17   ` John McCutchan
2004-05-10 22:31     ` Davide Libenzi
2004-05-10 22:41       ` John McCutchan
2004-05-10 22:52         ` Davide Libenzi [this message]
2004-05-10 23:10           ` Valdis.Kletnieks
2004-05-10 23:42             ` Davide Libenzi
2004-05-11  4:11         ` Chris Wedgwood
2004-05-11  2:00     ` Ian Kent
2004-05-11  2:47     ` Chris Wedgwood
2004-05-11 11:52       ` nf
2004-05-11 12:17         ` Stephen Rothwell
2004-05-11 12:24         ` John McCutchan
     [not found]         ` <1084278605.3839.47.camel@carados.180sw.com>
     [not found]           ` <1084885604.4062.48.camel@lilota.lamp.priv>
     [not found]             ` <1085127066.20393.440.camel@localhost.localdomain>
2004-05-21 12:04               ` nf
2004-05-11 12:20       ` John McCutchan
2004-05-11 12:46         ` viro
2004-05-11 19:02           ` John McCutchan
2004-05-11 20:28             ` carbonated beverage
2004-05-11 21:28               ` John McCutchan
2004-05-11 15:02       ` Alexander Larsson
2004-05-11 21:41         ` Chris Wedgwood
2004-05-12 12:38     ` Jörn Engel
2004-05-13 15:36 ` raven
2004-05-13 19:04   ` Chris Wedgwood
2004-05-14  7:04     ` Ian Kent
2004-05-13 21:24   ` John McCutchan
2004-05-14  2:02     ` Ian Kent
2004-05-15  4:52 ` raven

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=Pine.LNX.4.58.0405101548230.1156@bigblue.dev.mdolabs.com \
    --to=davidel@xmailserver.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ttb@tentacle.dhs.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

all inboxes | Powered by JetHome®