public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: cygcheck's understanding of TZ
Date: Mon, 13 Jun 2011 15:34:00 -0000	[thread overview]
Message-ID: <20110613153344.GA19880@ednor.casa.cgf.cx> (raw)
In-Reply-To: <BANLkTikhZ+tHjNzWZNM9VKN6b0Ei84FeWQ@mail.gmail.com>

On Mon, Jun 13, 2011 at 10:06:46AM -0500, Edward McGuire wrote:
>> On 2011-06-10 16:21, Christopher Faylor wrote:
>>> we still have no idea [...] why you find it so crucial for
>>> cygcheck to report the date with pinpoint accuracy
>
>On Fri, Jun 10, 2011 at 12:44, Denis Excoffier wrote:
>> Wrong by 1h is not pinpoint accuracy (i think).
>
>I realize I don't have a vote, but I disagree with your patch. Idiot
>proofing cygcheck(1) by forcing GMT on the user is overkill.
>cygcheck(1) only gives invalid output when it gets invalid input.
>Did cygcheck(1) and date(1) both give valid output with
>TZ=CET-1CEST?

FWIW, I'm not going to apply the patch.  I may think about accepting a
patch which displays the current timezone along with the current time or
which causes cygcheck to understand Cygwin's TZ usage but there is no
reason to force the date to UTC.  It's supposed to be the "Current
System Time" and that implies that it's the time the user expects when
they look at the clock on their wall.

I'm trying to be accommodating in case there is a valid concern lurking
somewhere here but so far I think this whole discussion is really rather
tempest in a teapot-y.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2011-06-13 15:34 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-09  7:47 EXCOFFIER Denis
2011-06-09  7:54 ` Thomas Wolff
2011-06-09 17:44   ` Buchbinder, Barry (NIH/NIAID) [E]
2011-06-09 17:39 ` Edward McGuire
2011-06-09 18:08   ` Charles Wilson
2011-06-09 19:27     ` Edward McGuire
2011-06-09 19:50       ` Denis Excoffier
2011-06-09 21:06         ` Christopher Faylor
2011-06-09 22:01           ` Edward McGuire
2011-06-10  7:25           ` Denis Excoffier
2011-06-10 14:07             ` Edward McGuire
2011-06-10 14:30             ` Christopher Faylor
2011-06-10 17:44               ` Denis Excoffier
2011-06-13 15:07                 ` Edward McGuire
2011-06-13 15:34                   ` Christopher Faylor [this message]
2011-06-14 15:05                     ` Lee Maschmeyer
2011-06-14 15:28                       ` Christopher Faylor
2011-06-14 17:30                         ` Lee Maschmeyer
2011-06-14 17:51                           ` Edward McGuire
2011-06-14 18:35                             ` Lee Maschmeyer
2011-06-14 19:19                               ` Edward McGuire
2011-06-14 19:22                                 ` Christopher Faylor
2011-06-14 19:21                           ` Christopher Faylor
2011-06-09 18:58   ` Christopher Faylor

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=20110613153344.GA19880@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@cygwin.com \
    --cc=cygwin@cygwin.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).