Lisi:
>
> I have an idea that there may be some distinction at the atomic level
> between UTC and GMT. Can anyone enlighten me? Or was the decision to
> call it UTC in place of GMT purely political?
Ah, time for my favourite quote from the Java6 API documentation:
| Some computer standards ar
On Thursday 02 December 2010 09:39:46 Lisi wrote:
> I have an idea that there may be some distinction at the atomic level
> between UTC and GMT. Can anyone enlighten me?
Thanks, Chris - you foresaw my question and answered it before I asked it. ;-)
Lisi
--
To UNSUBSCRIBE, email to debian-user
On Thursday 04 November 2010 15:23:13 Rodolfo Medina wrote:
> Chris Jackson writes:
> > File timestamps are (or at least should be) stored in UTC. It's the
> > display of them that's affected.
>
> But I did the following experiment: on a computer with system time set to
> UTC, I created a file at
On Thu, 04 Nov 2010 15:23:13 +, Rodolfo Medina wrote:
> Chris Jackson writes:
>
>> File timestamps are (or at least should be) stored in UTC. It's the
>> display of them that's affected.
>
>
>
> But I did the following experiment: on a computer with system time set
> to UTC, I created a fi
Chris Jackson writes:
> File timestamps are (or at least should be) stored in UTC. It's the
> display of them that's affected.
But I did the following experiment: on a computer with system time set to UTC,
I created a file at 14:43 UTC. Then I copied it via rsync and ethernet cross
cable to a
File timestamps are stored in UTC and converted to your local zone for
display. Thus they should jump when you change your timezone. They
should not change when the change to or from Daylight Savings Time
("Summer Time") occurs as that is not a change of zone but rather part
of the definition of
On Tue, 02 Nov 2010 19:26:48 +0100, Rodolfo Medina wrote:
> Rodolfo Medina wrote:
>
>> Last sunday, in my time zone (Rome), clocks were got back by one hour.
>> I noticed that my Debian Lenny had done so automatically, but files
>> timestamps were also took back by one hour, which is not what we
Mario Kleinsasser wrote:
> I'am in UTC+1 (currently normal time in Europe)
Normal time for most of Western Europe, certainly. But not for Portugal,
the Irish Republic, or the UK.
Regards,
Chris
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe".
Rodolfo Medina wrote:
> Last sunday, in my time zone (Rome), clocks were got back by one hour. I
> noticed that my Debian Lenny had done so automatically, but files timestamps
> were also took back by one hour, which is not what we want.
Camaleón writes:
> How is that? Do you have a proof of
On Tue, 02 Nov 2010 13:10:23 +0100, Rodolfo Medina wrote:
> Last sunday, in my time zone (Rome), clocks were got back by one hour.
Also here (Spain).
> I noticed that my Debian Lenny had done so automatically, but files
> timestamps were also took back by one hour, which is not what we want.
H
On Tue, Nov 2, 2010 at 1:48 PM, Chris Jackson wrote:
> Rodolfo Medina wrote:
>
> > Hallo.
> >
> > Last sunday, in my time zone (Rome), clocks were got back by one hour. I
> > noticed that my Debian Lenny had done so automatically, but files
> timestamps
> > were also took back by one hour, which
Rodolfo Medina wrote:
> Hallo.
>
> Last sunday, in my time zone (Rome), clocks were got back by one hour. I
> noticed that my Debian Lenny had done so automatically, but files timestamps
> were also took back by one hour, which is not what we want.
File timestamps are (or at least should be) s
Hallo.
Last sunday, in my time zone (Rome), clocks were got back by one hour. I
noticed that my Debian Lenny had done so automatically, but files timestamps
were also took back by one hour, which is not what we want.
Would it be possible to avoid that in future, and how?
In internet I only foun
13 matches
Mail list logo
