public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: pthread_cond_timedwait with setclock(CLOCK_MONOTONIC) times out early
Date: Sun, 02 Dec 2018 11:34:00 -0000	[thread overview]
Message-ID: <20181202113444.GW30649@calimero.vinschen.de> (raw)
In-Reply-To: <e5130a7a-3733-d835-127b-c1d453e15689@SystematicSw.ab.ca>

[-- Attachment #1: Type: text/plain, Size: 2090 bytes --]

On Dec  1 08:49, Brian Inglis wrote:
> On 2018-12-01 02:53, Corinna Vinschen wrote:
> > On Nov 30 21:27, Brian Inglis wrote:
> >> $ head /{etc,usr/lib}/os-release
> >> ==> /etc/os-release <==
> >> PRETTY_NAME="Debian GNU/Linux 9 (stretch)"
> >> NAME="Debian GNU/Linux"
> >> VERSION_ID="9"
> >> VERSION="9 (stretch)"
> >> ID=debian
> >> HOME_URL="https://www.debian.org/"
> >> SUPPORT_URL="https://www.debian.org/support"
> >> BUG_REPORT_URL="https://bugs.debian.org/"
> >>
> >> ==> /usr/lib/os-release <==
> >> ... [same]
> >>
> >> Could also be supported under Cygwin:
> > 
> > We don't have OS releases.  Every component in Cygwin has its own
> > release cycle and the version number of the Cygwin DLL is *not* a
> > os release number.  What sense would this file have for us?
> 
> Cygwin to me is a Unix package distro which provides bits and flavours of POSIX,
> Linux, and BSD userlands and APIs, that happens to be based on top of Windows,
> and provides extensive functionality and interoperability with and under that
> environment, which makes it easier working for or in many orgs and with most
> users and systems.
> 
> The Cygwin release is similar to Linux kernel versions, which may vary
> independent of distros and releases, but is also similar to distro releases like
> Debian 10 Buster or Ubuntu 19 Disco Dingo, which mark the time and progress e.g.
> 1.0 (RTM), 1.5 (Legacy), 1.7 (No9x/IPv6/LSA/charsets/IPC), 2.0 (NoPasswd), 2.5.2
> (LastXP), 2.6 (PostXP/Locales), 2.10 (NoKR/ssp/FORTIFY), ... in somewhat
> arbitrary steps.

But this is all Cygwin DLL version.  Nothing of that is related to
any kind of distro version number.  All other packages have their
own, entirely disconnected rolling release cycle.

If you like you can provide an os-release package with this file.
However, it would be kind of static:

  NAME=Cygwin
  VERSION="42"
  ID=cygwin
  VERSION_ID=42
  PRETTY_NAME="Cygwin"
  HOME_URL="https://cygwin.com/"
  SUPPORT_URL="https://cygwin.com/"


Corinna

-- 
Corinna Vinschen
Cygwin Maintainer

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2018-12-02 11:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-25 14:01 James E. King III
2018-11-26 15:35 ` Corinna Vinschen
2018-11-26 15:47   ` James E. King III
2018-11-26 16:47     ` Corinna Vinschen
2018-11-29 10:18       ` Corinna Vinschen
2018-11-29 22:39         ` James E. King III
2018-11-30 12:14           ` Corinna Vinschen
2018-11-30 12:44             ` James E. King III
2018-11-30 12:56               ` Corinna Vinschen
2018-12-01  4:27                 ` Brian Inglis
2018-12-01  9:53                   ` Corinna Vinschen
2018-12-01 15:49                     ` Brian Inglis
2018-12-02 11:34                       ` Corinna Vinschen [this message]

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=20181202113444.GW30649@calimero.vinschen.de \
    --to=corinna-cygwin@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).