From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: mtk.manpages@gmail.com, "Theodore Ts'o" <tytso@mit.edu>,
Eric Sandeen <sandeen@redhat.com>,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
Linux btrfs Developers List <linux-btrfs@vger.kernel.org>,
XFS Developers <xfs@oss.sgi.com>,
linux-man@vger.kernel.org,
Linux-Fsdevel <linux-fsdevel@vger.kernel.org>,
Linux API <linux-api@vger.kernel.org>
Subject: Re: Documenting MS_LAZYTIME
Date: Tue, 03 Mar 2015 08:14:08 +0100 [thread overview]
Message-ID: <54F55F40.6010508@gmail.com> (raw)
In-Reply-To: <20150227175159.GC11031@birch.djwong.org>
On 02/27/2015 06:51 PM, Darrick J. Wong wrote:
> On Fri, Feb 27, 2015 at 09:01:10AM +0100, Michael Kerrisk (man-pages) wrote:
>> On 02/27/2015 01:04 AM, Theodore Ts'o wrote:
>>> On Thu, Feb 26, 2015 at 02:36:33PM +0100, Michael Kerrisk (man-pages) wrote:
>>>>
>>>> The disadvantage of MS_STRICTATIME | MS_LAZYTIME is that
>>>> in the case of a system crash, the atime and mtime fields
>>>> on disk might be out of date by at most 24 hours.
>>>
>>> I'd change to "The disadvantage of MS_LAZYTIME is that..." and
>>> perhaps move that so it's clear it applies to any use of MS_LAZYTIME
>>> has this as a downside.
>>>
>>> Does that make sense?
>>
>> Thanks, Ted. Got it. So, now we have:
>>
>> MS_LAZYTIME (since Linux 3.20)
>
> "since Linux 4.0".
D'oh! Yes, thanks. Fixed.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2015-03-03 7:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 8:50 Documenting MS_LAZYTIME Michael Kerrisk
2015-02-20 12:32 ` Andreas Dilger
2015-02-20 13:22 ` Michael Kerrisk (man-pages)
2015-02-20 15:49 ` Eric Sandeen
2015-02-21 2:56 ` Theodore Ts'o
2015-02-23 12:20 ` Austin S Hemmelgarn
2015-02-23 16:24 ` Eric Sandeen
2015-02-26 8:53 ` Michael Kerrisk (man-pages)
2015-02-26 8:49 ` Michael Kerrisk (man-pages)
2015-02-26 13:31 ` Theodore Ts'o
2015-02-26 13:36 ` Michael Kerrisk (man-pages)
2015-02-27 0:04 ` Theodore Ts'o
2015-02-27 8:01 ` Michael Kerrisk (man-pages)
2015-02-27 8:08 ` Omar Sandoval
2015-02-27 8:36 ` Michael Kerrisk (man-pages)
2015-02-27 14:18 ` Theodore Ts'o
2015-02-27 17:51 ` Darrick J. Wong
2015-03-03 7:14 ` Michael Kerrisk (man-pages) [this message]
2015-02-21 7:57 ` Michael Kerrisk (man-pages)
2015-02-22 18:30 ` Robert White
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=54F55F40.6010508@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=darrick.wong@oracle.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=tytso@mit.edu \
--cc=xfs@oss.sgi.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 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).