From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Hans Ronne <hronne@comhem.se>
Cc: Jim Kingdon <kingdon@panix.com>, <xconq7@sources.redhat.com>
Subject: Re: Newest code crashes Tcl/Tk
Date: Thu, 24 Jun 2004 17:30:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0406241304290.13454-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <l03130301bd00b71c4c5f@[212.181.162.155]>
On Thu, 24 Jun 2004, Hans Ronne wrote:
> >> That's strange. When I do the same thing, my first entry is:
> >
> >Probably timezones. I don't remember how CVS handles them in this
> >context.
>
> Right. But this makes no sense. CVS should use local time or possibly GMT
> to date a checkin. The checkin date should not depend on who is checking
> out the code. In fact, if this is what is going on, I would call it a bug
> in CVS.
Well, if it's a bug, then it is a very well-documented one. :-)
From my CVS manpage:
-D date_spec
Use the most recent revision no later than date_spec (a single
argument, date description specifying a date in the past). A
wide variety of date formats are supported, in particular ISO
("1972-09-24 20:05") or Internet ("24 Sep 1972 20:05"). The
date_spec is interpreted as being in the local timezone, unless
a specific timezone is specified.
[snipped, examples below]
3/31/92 10:00:07 PST
22:00 GMT
To get everyone on the same page, maybe we should be doing
checkouts or updates with the date specifier and "0:00 GMT".
Eric
next prev parent reply other threads:[~2004-06-24 17:08 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 6:50 GDL Notice: Arithmetic Operators / Quasi-Formulae Eric McDonald
2004-06-21 8:11 ` Newest code crashes Tcl/Tk Brian Dunn
2004-06-21 16:22 ` Eric McDonald
2004-06-21 20:13 ` Hans Ronne
2004-06-24 0:04 ` Brian Dunn
2004-06-24 3:36 ` Hans Ronne
2004-06-24 4:21 ` Brian Dunn
2004-06-24 4:50 ` Eric McDonald
2004-06-24 6:28 ` Brian Dunn
2004-06-24 18:34 ` Eric McDonald
2004-06-24 7:15 ` Hans Ronne
2004-06-24 9:28 ` Brian Dunn
2004-06-24 9:41 ` Tcl/Tk update Brian Dunn
2004-06-24 17:08 ` Hans Ronne
2004-06-24 15:01 ` Tck/Tk info Brian Dunn
2004-06-27 6:16 ` Brian Dunn
2004-06-27 9:19 ` Hans Ronne
2004-06-24 16:59 ` Newest code crashes Tcl/Tk Jim Kingdon
2004-06-24 17:03 ` Hans Ronne
2004-06-24 17:30 ` Eric McDonald [this message]
2004-06-24 18:24 ` Hans Ronne
2004-06-21 16:25 ` GDL Notice: Arithmetic Operators / Quasi-Formulae Eric McDonald
2004-06-22 3:25 ` Eric McDonald
2004-06-22 6:19 ` Jim Kingdon
2004-06-22 9:50 ` Juergen Ruehle
2004-06-22 14:18 ` RFC: Increment and Decrement (was Re: GDL Notice: Arithmetic Operators / Quasi-Formulae) Eric McDonald
2004-06-22 14:50 ` Jim Kingdon
2004-06-23 6:02 ` Eric McDonald
2004-06-23 6:17 ` Jim Kingdon
2004-06-23 13:40 ` RFC: Increment and Decrement (was Re: GDL Notice: ArithmeticOperators " Erik Jessen
2004-06-23 23:33 ` Autotesting (was Re: RFC: Increment and Decrement) Eric McDonald
2004-06-24 7:01 ` Jim Kingdon
2004-06-25 3:35 ` Eric McDonald
2004-06-22 14:03 ` GDL Notice: Arithmetic Operators / Quasi-Formulae Eric McDonald
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=Pine.LNX.4.44.0406241304290.13454-100000@leon.phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=hronne@comhem.se \
--cc=kingdon@panix.com \
--cc=xconq7@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).