9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: arisawa <arisawa@ar.aichi-u.ac.jp>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] curious mtime of cwfs
Date: Mon, 25 Feb 2013 20:39:15 +0900	[thread overview]
Message-ID: <9622CBBC-AB42-4620-A9F4-26925ADD998E@ar.aichi-u.ac.jp> (raw)
In-Reply-To: <20130225103415.GA21986@dinah>

thanks Anthony,

I understand the behavior of fossil.
cwfs is out of the rule.

I said:
  standing on general rule of unix and plan9,
  mtime of directory should be the time that the contents are modified.
but this is not true in rigorous speaking.

Kenji Arisawa

On 2013/02/25, at 19:34, Anthony Martin <ality@pbrane.org> wrote:

> cinap_lenrek@gmx.de once said:
>> i'm not sure. if you touch an existing file, then it makes sense
>> that the files mtime gets updated, not the whole directory.
>>
>> wstat() and write() on a file only update the files mtime, not
>> the parent directory.
>>
>> however creating a new file or deleting a file from a directory
>> does change the directories mtime. (the dump change makes it
>> consistent with that).
>
> From stat(5):
>
>    For a plain file, mtime is the time of the most recent
>    create, open with truncation, or write; for a directory
>    it is the time of the most recent remove, create, or
>    wstat of a file in the directory.
>
> Cheers,
>  Anthony
>




  parent reply	other threads:[~2013-02-25 11:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-25  1:04 arisawa
2013-02-25  1:17 ` arisawa
2013-02-25  5:55   ` cinap_lenrek
2013-02-25  7:24     ` arisawa
2013-02-25  8:23       ` cinap_lenrek
2013-02-25 10:17         ` arisawa
2013-02-25 10:34         ` Anthony Martin
2013-02-25 11:27           ` cinap_lenrek
2013-02-25 11:39           ` arisawa [this message]
2013-03-02 21:08           ` erik quanstrom
2013-03-03  3:30             ` arisawa

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=9622CBBC-AB42-4620-A9F4-26925ADD998E@ar.aichi-u.ac.jp \
    --to=arisawa@ar.aichi-u.ac.jp \
    --cc=9fans@9fans.net \
    /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).