From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 111891] access to file does not change access time to folders above up to /(root)
Date: Fri, 05 Feb 2016 08:31:20 +0000 [thread overview]
Message-ID: <bug-111891-13602-fg7Ullaml5@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-111891-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=111891
--- Comment #3 from Armin Mohring <armin_mohring@web.de> ---
I think, only symbolic links should be used.
The parent directory is given by the directory tree itself. Stored in a tree.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2016-02-05 8:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 14:42 [Bug 111891] New: access to file does not change access time to folders above up to /(root) bugzilla-daemon
2016-02-05 2:38 ` [Bug 111891] " bugzilla-daemon
2016-02-05 2:58 ` bugzilla-daemon
2016-02-05 8:31 ` bugzilla-daemon [this message]
2016-02-05 20:36 ` bugzilla-daemon
2016-02-05 20:39 ` bugzilla-daemon
2016-02-07 9:59 ` bugzilla-daemon
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=bug-111891-13602-fg7Ullaml5@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.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).