9front - general discussion about 9front
 help / color / mirror / Atom feed
From: sl@stanleylieber.com
To: 9front@9front.org
Subject: mtime(1) vs deeply nested directories
Date: Mon, 9 Dec 2019 20:54:50 -0500	[thread overview]
Message-ID: <20191210015450.9OOztYI1qNAipKCgMIAcKg6uCtMjopqbQ901zjhTYF4@z> (raw)

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


                 reply	other threads:[~2019-12-10  1:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20191210015450.9OOztYI1qNAipKCgMIAcKg6uCtMjopqbQ901zjhTYF4@z \
    --to=sl@stanleylieber.com \
    --cc=9front@9front.org \
    /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).