public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: 2.3.0: possible Cygwin flock bug (Windows 10 x86_64)
Date: Mon, 16 Nov 2015 11:24:00 -0000	[thread overview]
Message-ID: <20151116112357.GC6402@calimero.vinschen.de> (raw)
In-Reply-To: <CACnvoQcwa_tOkPMzoQ7Tjgxoip2U=FE78eDFrPb0KjBfd=tDVg@mail.gmail.com>

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

On Nov 13 13:25, Mario Roy wrote:
> Hello Corinna,
> 
> I am writing to confirm that file locking, with MCE 1.608, utilizing
> the development snapshot 2015-11-12 x86_64 is passing 100%. I ran
> through other test cases including mixing threads and child processes.

Thanks for testing and confirming.  I uploaded the new Cygwin 2.3.1
already on Saturday.

> [...]
> MCE 1.700 in Github runs well with channel locking across the board.
> However, being able to obtain a shared lock (possible with file
> locking) at the application level is nice. Seeing the above example
> work makes me confident in bringing back file locking and know that it
> will work across platforms including Cygwin.

Sounds good.


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2015-11-16 11:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-12  2:51 Mario Roy
2015-11-12 12:28 ` Corinna Vinschen
2015-11-13 18:25   ` Mario Roy
2015-11-16 11:24     ` 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=20151116112357.GC6402@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).