public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: how to access and display apps that I've launched
Date: Wed, 26 Jul 2017 08:16:00 -0000	[thread overview]
Message-ID: <a588ade0-0d2c-d916-23ca-e7ea24b728be@SystematicSw.ab.ca> (raw)
In-Reply-To: <87tw20nzzx.fsf@Rainer.invalid>

On 2017-07-25 12:16, Achim Gratz wrote:
> Brian Inglis writes:
>> rebaselst uses touch -t 7001010000 ... - could be patched to 197001010000.
> 
> Could be, but touch is specified to assume "19" yhen YY=70 by POSIX, AFAIK.
> 
>> Is this affected by locale and by Windows regional date settings in Control
>> Panel/Region/Formats tab/Additional settings... button/Date tab/Calendar
>> group/When a two-digit year is entered, interpret it as a year between
>> |(nnnn-99)| and [nnnn ^v] with the default values |1980| and [2079 ^v] i.e. from
>> the start of the DOS epoch which postdates the Unix epoch 19700101, and could
>> cause 70 to be interpreted as 2070.
> 
> That would be surprising since the expectation really is UNIX epoch when
> we're talking about Cygwin.  In any case, the OP should easily be able
> to test this at the shell prompt.

I know POSIX says and my tests on current releases verify 1969-99, 2000-68, but
could this be thrown off by localization interfering in some cases, as was
/proc/loadavg, because a function started using locales?
These files and related functions do not seem candidates to be affected by the
recent patch for ls problems with symlinks, so BLODA blocking pre-1980 times?

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
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:[~2017-07-25 19:57 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1783227004.4348461.1500934105434.ref@mail.yahoo.com>
2017-07-24 22:49 ` Ian Lambert via cygwin
2017-07-25  0:03   ` mike
2017-07-25  4:27   ` Ken Brown
2017-07-25  4:55     ` Ian Lambert via cygwin
2017-07-25 15:06       ` Ken Brown
2017-07-25  5:21     ` Brian Inglis
2017-07-25 10:17       ` Brian Inglis
2017-07-25 11:57       ` Brian Inglis
2017-07-25 13:03       ` Brian Inglis
2017-07-25 14:13       ` Brian Inglis
2017-07-25 19:19       ` Achim Gratz
2017-07-26  8:16         ` Brian Inglis [this message]
2017-07-25 19:01     ` Achim Gratz
     [not found] <1128827672.1514648.1501092281786.ref@mail.yahoo.com>
2017-07-27 16:01 ` Ian Lambert via cygwin
     [not found] <1534921570.1524318.1501093009415.ref@mail.yahoo.com>
2017-07-27 14:49 ` Ian Lambert via cygwin
     [not found] <685307372.1339085.1501078785472.ref@mail.yahoo.com>
2017-07-26 17:09 ` Ian Lambert via cygwin
2017-07-26 17:13   ` Ken Brown
2017-07-26 18:27     ` Brian Inglis
2017-07-27  2:38   ` Achim Gratz
     [not found] <1036849022.821922.1501019281615.ref@mail.yahoo.com>
2017-07-26  9:50 ` Ian Lambert via cygwin
2017-07-26 10:28   ` Brian Inglis
     [not found] <799230527.525007.1500998733401.ref@mail.yahoo.com>
2017-07-25 18:21 ` Ian Lambert via cygwin
2017-07-25 21:52   ` Achim Gratz
2017-07-26  6:49   ` Ken Brown
     [not found] <1438727230.474852.1500993486132.ref@mail.yahoo.com>
2017-07-25 18:12 ` Ian Lambert via cygwin
2017-07-25 18:16   ` Ken Brown
2017-07-25 19:57   ` Achim Gratz
     [not found] <472748733.4076472.1500916852092.ref@mail.yahoo.com>
2017-07-24 19:46 ` Ian Lambert via cygwin
     [not found] <949225432.4024000.1500912514455.ref@mail.yahoo.com>
2017-07-24 18:07 ` Ian Lambert via cygwin
2017-07-24 20:22   ` Ken Brown
2017-07-23 14:25 mike
2017-07-23 17:39 ` Jack
2017-07-23 18:14   ` mike
2017-07-23 19:18     ` Brian Inglis
2017-07-23 19:46       ` mike
2017-07-24 17:31         ` Brian Inglis
2017-07-25  2:16           ` mike
2017-07-23 22:46 ` Ken Brown

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=a588ade0-0d2c-d916-23ca-e7ea24b728be@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).