On Thu, Jun 07, 2001 at 17:54 +0100, Kris Thielemans wrote:
>
> I'm bewildered by the reactions on Karsten's mail. Maybe it is
> because he doesn't really say what his setup is.
It could as well be because it's been a FAQ and has been
discussed to death a few thousand times. Searching the archi
Hi,
I'm bewildered by the reactions on Karsten's mail. Maybe it is because he
doesn't really say what his setup is.
In any case, I'd fully expect that NT gets the right time from the CVS,
whatever its timezone, and wherever the server is. This of course requires
that both the NT workstation and
Hi Karsten,
> Each time I commit a file, the timestamp is 2 hours off (also shown in
> wincvs). I guess it is because I am in the CET (GMT+1) and it is currently
> daylight saving (+1 hour) for the summer.
>
> The clock on my NT machine is set correctly to the current timezone and
> daylight sav
Karsten Aarrebo Pedersen writes:
>
> Since I am not going to do multi timezone development, I would like cvs to
> use the time Windows are using.
>
> Does anybody have a solution to this problem?
Move to England or rewrite CVS.
-Larry Jones
I wonder if I can grow fangs when my baby teeth fall
It sounds like you have to change the timezone your server is using.
That would be dependent on what OS you are using, which you didn't
mention the server configuration.
-- David F.
Karsten Aarrebo Pedersen wrote:
>
> I have installed cvs on a windows NT machine and have the following problem:
I have installed cvs on a windows NT machine and have the following problem:
Each time I commit a file, the timestamp is 2 hours off (also shown in
wincvs). I guess it is because I am in the CET (GMT+1) and it is currently
daylight saving (+1 hour) for the summer.
The clock on my NT machine is s
