9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Eric Van Hensbergen" <ericvh@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: Linux 9p timestamps
Date: Sun, 30 Jul 2006 22:20:02 -0500	[thread overview]
Message-ID: <a4e6962a0607302020w2a9c6c01ia191191698a81b59@mail.gmail.com> (raw)
In-Reply-To: <527cb238df9a41e8b1649fcacb723f94@quanstro.net>

On 7/30/06, erik quanstrom <quanstro@quanstro.net> wrote:
> yes.  unix and plan 9 both use seconds since epoch to
> represent the date and both use an epoch defined in the
> GMT timezone.
>
> there shouldn't be any conversion required as the timezone+dst
> offset needs to be added only for display.
>
> - erik
>
> On Sun Jul 30 14:51:52 CDT 2006, forsyth@vitanuova.com wrote:
> > >It would then be the responsibility of the client to adjust for
> > >his/her local time zone.
> >
> > isn't the value of ctime and mtime always in gmt, even on linux?
> > on unix it was only the programs calling ctime (or relatives)
> > that finally adjusted for local time, typically before displaying it.
> > i don't see how the client kernel would or should get involved.
>

okay - I'll bite -- so what's csant's problem then?

          -eric


  reply	other threads:[~2006-07-31  3:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-30  5:53 [9fans] " csant
2006-07-30 15:18 ` [9fans] " Eric Van Hensbergen
2006-07-30 19:48   ` C H Forsyth
2006-07-30 22:17     ` erik quanstrom
2006-07-31  3:20       ` Eric Van Hensbergen [this message]
2006-07-31  7:27         ` Steve Simon
2006-07-31 18:50           ` erik quanstrom
2006-07-31 19:27             ` Lluís Batlle
2006-07-31 20:24               ` csant
2006-07-31 20:57                 ` Steve Simon
2006-07-31 22:04                   ` csant
2006-07-31 22:33                     ` erik quanstrom
2006-07-31 23:06                       ` csant
2006-07-31 22:12               ` Anthony Sorace

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=a4e6962a0607302020w2a9c6c01ia191191698a81b59@mail.gmail.com \
    --to=ericvh@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).