From: barry bouwsma <free_beer_for_all@yahoo.com>
To: linux-kernel@vger.kernel.org
Cc: Joe Peterson <joe@skyrush.com>
Subject: Re: [PATCH] UTC timestamp option for FAT filesystems
Date: Wed, 25 Jun 2008 06:31:14 -0700 (PDT) [thread overview]
Message-ID: <223222.41388.qm@web46108.mail.sp1.yahoo.com> (raw)
Moin moin!
May I just add a resounding YES-YES-YES to the message which was
posted earlier today as
Message-ID: <>
oh b*gger, that doesn't help when snarfing from a web archive
(voluntary use as a non-subscirber of a webmail interface prevents
me from including a References: header without more effort than I
care to do now, not that this would help)
I was actually just about to post an almost identical message today
to clean out my repository of hacks, with almost the same justifications.
In addition, may I request that not only the option `-o utc,...' be
accepted, but also as an alternate, the string `gmt', not because it's
more accurate (it isn't) but because it seems to be tradition to use
GMT+/-xxxx in lots of places.
Another justification which wasn't mentioned, but which I would put
forth, is that last time I checked, the BSDen were using UTC as their
MSDOS timestamp base, so such an option would make it easier to
exchange data between BSD and Linux machines with a normal USB stick
or flash card. And I was doing that a year or three ago when I hacked
my hack.
I'll have to do a line-by-line comparison with my hacked code (last
applied to 2.6.24-ish) to make sure I don't have any differences, but
in order to allow users the option to specify the seeped-in-tradition-
especially-for-us-old-f*rts `gmt', here's the trivial-to-correct
section of code -- may well be different than in the patch since I
didn't save it before being kicked offline:
in fs/fat/inode.c
880 {Opt_debug, "debug"},
881 {Opt_immutable, "sys_immutable"},
882 /* XXX HACK */
883 {Opt_utc, "utc"},
884 {Opt_utc, "gmt"},
885 {Opt_obsolate, "conv=binary"},
886 {Opt_obsolate, "conv=text"},
(I use `-o utc' myself but would prefer to be flexible to alternate uses)
I notice this most when I fail to include the needed patches when
updating kernel
thanks
barry bouwsma
next reply other threads:[~2008-06-25 13:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 13:31 barry bouwsma [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2008-06-25 5:24 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
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
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=223222.41388.qm@web46108.mail.sp1.yahoo.com \
--to=free_beer_for_all@yahoo.com \
--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
Powered by JetHome