public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Joe Peterson <joe@skyrush.com>
Cc: Andi Kleen <andi@firstfloor.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] UTC timestamp option for FAT filesystems
Date: Fri, 27 Jun 2008 01:26:00 +0900	[thread overview]
Message-ID: <87zlp8w4br.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <4863B9AF.4080105@skyrush.com> (Joe Peterson's message of "Thu, 26 Jun 2008 09:45:51 -0600")

Joe Peterson <joe@skyrush.com> writes:

> I do not consider this modifying the design of FAT.  FAT does not have
> the concept of time zone, DST, or UTC.  It is just a date/time (stamped
> on the volume with no info about what that means).  It is customary to
> say these times are in local time, and Windows happens to use it as if
> it's straight local time (Linux tries to emulate this).  But using FAT
> to store UTC instead is not changing the design, it is just using it
> differently.  I agree this would not be a good idea when sharing a
> volume with Windows, but for cameras, e.g., why not?

UTC itself is not wrong. But, I think *"utc" option* is not way to go.

>> However, I can accept that hack for many broken devices on realworld,
>> but, the modifying design is not right option. Do you see what I want
>> to say?
>
> If it is a hack (and I do not consider it to be so), I still do not see
> why the utc option is a design change - how else would you get the
> desired behavior?

I think we agreed to fix sys_tz is good thing.

If so, I'd like to see "tz=xxx" or something for the future, instead of
"utc", don't you think so? I really hate to add the random options.
-- 
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>

  reply	other threads:[~2008-06-26 16:26 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-25  5:24 [PATCH] UTC timestamp option for FAT filesystems Joe Peterson
2008-06-25 22:33 ` Andi Kleen
2008-06-25 23:56   ` Joe Peterson
2008-06-26  2:44     ` Joe Peterson
2008-06-26  7:32       ` OGAWA Hirofumi
2008-06-26 13:23         ` Joe Peterson
2008-06-26 14:37           ` OGAWA Hirofumi
2008-06-26 15:45             ` Joe Peterson
2008-06-26 16:26               ` OGAWA Hirofumi [this message]
2008-06-26 17:06                 ` Joe Peterson
2008-06-28 22:24                   ` James Cloos
2008-06-29  5:03                     ` Joe Peterson
2008-06-29  8:20                       ` Bernd Eckenfels
2008-06-26 17:21                 ` Joe Peterson
2008-06-26 18:15                   ` OGAWA Hirofumi
2008-06-27  5:12                   ` Joe Peterson
2008-07-01 23:25                     ` Andrew Morton
2008-07-02  4:43                       ` Joe Peterson
2008-07-01 23:27                     ` Andrew Morton
2008-07-02 14:47                       ` Joe Peterson
2008-06-26 16:01             ` Joe Peterson
2008-06-26 17:08               ` OGAWA Hirofumi
  -- strict thread matches above, loose matches on Subject: below --
2008-06-25 13:31 barry bouwsma
2008-06-25 14:42 ` Joe Peterson
2008-06-25 19:35   ` barry bouwsma
2008-06-26  4:24     ` Joe Peterson
2008-06-26 19:07       ` barry bouwsma

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=87zlp8w4br.fsf@devron.myhome.or.jp \
    --to=hirofumi@mail.parknet.co.jp \
    --cc=andi@firstfloor.org \
    --cc=joe@skyrush.com \
    --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