From mboxrd@z Thu Jan  1 00:00:00 1970
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: arisawa <arisawa@ar.aichi-u.ac.jp>
In-Reply-To: <20130225103415.GA21986@dinah>
Date: Mon, 25 Feb 2013 20:39:15 +0900
Content-Transfer-Encoding: 7bit
Message-Id: <9622CBBC-AB42-4620-A9F4-26925ADD998E@ar.aichi-u.ac.jp>
References: <06B26204-D2D9-4438-8EB3-603B88F8B03C@ar.aichi-u.ac.jp>
	<6b8af56ccf29a8e293aefcc39c79576f@rei2.9hal>
	<20130225103415.GA21986@dinah>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] curious mtime of cwfs
Topicbox-Message-UUID: 1ec4bd24-ead8-11e9-9d60-3106f5b1d025

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
>