From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] watch command
Date: Tue, 19 Apr 2005 17:53:13 +0200 [thread overview]
Message-ID: <3877c569deb6f9b6dd7e323ee5a568d6@proxima.alt.za> (raw)
In-Reply-To: <aeed997883de6ac00c1b53e9476ba020@plan9.escet.urjc.es>
> We tried with a change for fossil to tell about changes, but we
> found that a change (suggested by rsc in the source) to propagate
> mtimes upwards in the tree up to the root made it trivial to learn which
> files changed since the last scan. BTW, our poll is not using that feature.
That would be the key, wouldn't it? If one could hook into the
fileserver to detect mtime changes, one would have the mechanism for
notification. Possible? I should think that the difficult part is to
stick to the Plan 9 way to do things.
++L
next prev parent reply other threads:[~2005-04-19 15:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-19 8:59 YAMANASHI Takeshi
2005-04-19 9:19 ` Fco. J. Ballesteros
2005-04-19 10:06 ` Charles Forsyth
2005-04-19 15:01 ` Ronald G. Minnich
2005-04-19 15:23 ` Fco. J. Ballesteros
2005-04-19 15:53 ` Lucio De Re [this message]
2005-04-19 15:59 ` Dan Cross
2005-04-19 16:02 ` Steve Simon
2005-04-19 16:23 ` boyd, rounin
2005-04-19 15:00 ` Ronald G. Minnich
-- strict thread matches above, loose matches on Subject: below --
2005-04-21 0:37 YAMANASHI Takeshi
2005-04-20 2:09 YAMANASHI Takeshi
2005-04-20 5:14 ` Ronald G. Minnich
2005-04-20 15:06 ` Ronald G. Minnich
2005-04-20 2:07 YAMANASHI Takeshi
2005-04-20 1:55 YAMANASHI Takeshi
2005-04-19 10:50 YAMANASHI Takeshi
2005-04-19 7:13 YAMANASHI Takeshi
2005-04-19 6:57 YAMANASHI Takeshi
2005-04-19 10:47 ` Abhey Shah
2005-04-19 6:49 YAMANASHI Takeshi
2005-04-19 6:50 ` Kenji Okamoto
2005-04-19 6:55 ` boyd, rounin
2005-04-19 6:17 YAMANASHI Takeshi
2005-04-19 6:37 ` Kenji Okamoto
2005-04-19 8:35 ` Fco. J. Ballesteros
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=3877c569deb6f9b6dd7e323ee5a568d6@proxima.alt.za \
--to=lucio@proxima.alt.za \
--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).