From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Namjae Jeon <linkinjeon@gmail.com>
Cc: akpm@linux-foundation.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org,
Amit Sahrawat <amit.sahrawat83@gmail.com>
Subject: Re: [PATCH 2/3] fat: fix time updates for create and delete
Date: Mon, 12 Nov 2012 16:58:01 +0900 [thread overview]
Message-ID: <87obj35k3a.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <87sj8f5k4m.fsf@devron.myhome.or.jp> (OGAWA Hirofumi's message of "Mon, 12 Nov 2012 16:57:13 +0900")
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> writes:
> Namjae Jeon <linkinjeon@gmail.com> writes:
>
>> 2012/11/12, OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>:
>>> Namjae Jeon <linkinjeon@gmail.com> writes:
>>>
>>>> Correctly update modification and status change time in case of
>>>> file/directory removal and creation.
>>>
>>> This changelog just explain "what", and it doesn't explain "why". Please
>>> explain why we need this change.
>>>
>>> IIRC, timestamp handling in FAT driver is strange historically. Anyway,
>>> FAT doesn't have "inode change time". It is "creation time" in FAT.
>> Hi. OGAWA.
>> I made this patch after comparing timestamp handlings with MSDOS and XFS.
>> Should timestamp handling of FAT be same with MSDOS ?
>> Am I missing ?
>
> What was difference with XFS, FAT, and MSDOS?
BTW, I recall I checked this, and yes, it is strange. But it is historical.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2012-11-12 7:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-11 13:57 [PATCH 2/3] fat: fix time updates for create and delete Namjae Jeon
2012-11-11 16:09 ` OGAWA Hirofumi
2012-11-12 6:37 ` Namjae Jeon
2012-11-12 7:57 ` OGAWA Hirofumi
2012-11-12 7:58 ` OGAWA Hirofumi [this message]
2012-11-12 9:12 ` Namjae Jeon
2012-11-12 9:21 ` OGAWA Hirofumi
2012-11-12 9:22 ` OGAWA Hirofumi
2012-11-15 7:02 ` Namjae Jeon
2012-11-15 7:18 ` OGAWA Hirofumi
2012-11-16 10:12 ` Namjae Jeon
2012-11-16 13:47 ` OGAWA Hirofumi
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=87obj35k3a.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=akpm@linux-foundation.org \
--cc=amit.sahrawat83@gmail.com \
--cc=linkinjeon@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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).