From: "Fco. J. Ballesteros" <nemo@lsub.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] some shell scripts
Date: Thu, 14 Oct 2004 11:22:48 +0200 [thread overview]
Message-ID: <f45cbdd4568702828fa0549146e512f2@plan9.escet.urjc.es> (raw)
In-Reply-To: <20041014105926.08edbf1f.martin_ml@parvat.com>
> This pretty-much requires a mechanism for the kernel to tell a user
> process about changes to the filesystem, which sounds horrible, but
One of the things in my todo is doing something to notify changes
in the fs. It could be either a change in fossil or a wrapper fs to notify
events. Somehow I managed to skip this issue so far.
prev parent reply other threads:[~2004-10-14 9:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 22:38 Russ Cox
2004-10-14 5:29 ` Martin C.Atkins
2004-10-14 6:50 ` geoff
2004-10-14 9:56 ` Martin C.Atkins
2004-10-14 15:29 ` Nigel Roles
2004-10-15 0:25 ` geoff
2004-10-15 0:28 ` Russ Cox
2004-10-15 0:38 ` geoff
2004-10-14 9:22 ` Fco. J. Ballesteros [this message]
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=f45cbdd4568702828fa0549146e512f2@plan9.escet.urjc.es \
--to=nemo@lsub.org \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).