From: Valerie Henson <val_henson@linux.intel.com>
To: Michael Kerrisk <mtk-manpages@gmx.net>
Cc: val_henson@linux.interl.com, lkml <linux-kernel@vger.kernel.org>
Subject: Re: Documenting MS_RELATIME
Date: Sun, 11 Feb 2007 22:53:13 -0800 [thread overview]
Message-ID: <20070212065312.GB20919@nifty> (raw)
In-Reply-To: <45CE0737.6010103@gmx.net>
On Sat, Feb 10, 2007 at 09:56:07AM -0800, Michael Kerrisk wrote:
> Val,
>
> I'm just updating the mount(2) man page for MS_RELATIME, and this is the
> text I've come up with:
>
> MS_RELATIME(Since Linux 2.6.20)
> When a file on this file system is accessed, only
> update the file's last accessed time (atime) if
> the current value of atime is less than or equal
> to the file's last modified (mtime) or last sta-
> tus change time (ctime). This option is useful
> for programs, such as mutt(1), that need to know
> when a file has been read since it was last modi-
> fied.
>
> This text is based on your comments accompanying the various patches, but
> it differs in a respect. Your comments said that the atime would only be
> updated if the atime is older than mtime/ctime. However, what the code
> actually does is update atime if it is is <= mtime/ctime -- i.e., atime is
> older than or *or equal to* mtime/ctime.
>
> I'm sure that the code implements your intention, but before incorporating
> the above text I thought I just better check, since the code differs from
> your comment. Can you just confirm that the proposed man page text is okay.
That's correct, yes. Thanks!
-VAL
prev parent reply other threads:[~2007-02-12 6:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-10 17:56 Documenting MS_RELATIME Michael Kerrisk
2007-02-11 0:54 ` Dave Jones
2007-02-12 6:55 ` Valerie Henson
2007-02-12 15:40 ` Dave Jones
2007-02-12 17:49 ` Jan Engelhardt
2007-02-12 17:55 ` Jörn Engel
2007-02-12 19:53 ` Petri Kaukasoina
2007-02-12 19:57 ` Valerie Henson
2007-02-12 19:42 ` Valerie Henson
2007-02-12 6:53 ` Valerie Henson [this message]
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=20070212065312.GB20919@nifty \
--to=val_henson@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk-manpages@gmx.net \
--cc=val_henson@linux.interl.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.