From mboxrd@z Thu Jan  1 00:00:00 1970
Subject: mtime(1) vs deeply nested directories
Date: Mon, 9 Dec 2019 20:54:50 -0500
From: sl@stanleylieber.com
To: 9front@9front.org
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: information-aware STM optimizer 
Message-ID: <20191210015450.9OOztYI1qNAipKCgMIAcKg6uCtMjopqbQ901zjhTYF4@z>

help:

file system is hjfs.

; date -m `{mtime 2019 | awk '{print $1}'}
Tue, 03 Dec 2019 21:55:01 -0500
; date -m `{mtime 2019/12 | awk '{print $1}'}
Thu, 05 Dec 2019 23:57:30 -0500
; date -m `{mtime 2019/12/03 | awk '{print $1}'}
Tue, 03 Dec 2019 21:55:01 -0500
; date -m `{mtime 2019/12/05 | awk '{print $1}'}
Thu, 05 Dec 2019 23:57:30 -0500

why does mtime(1) run against the top-level 2019/ directory show it
was modified at exactly the same time as 2019/12/03/, while 2019/12/
shows it was modified at exactly the same time as 2019/12/05/?

shouldn't 2019/ show it was modified at the same time as 2019/12/05/
(this was the last directory modified under 2019/)?

both directories 2019/ and 2019/12/ already existed before 2019/03/
and 2019/05/ were created.

sl