public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST: Cygwin 3.0.0-0.3
Date: Mon, 04 Feb 2019 14:25:00 -0000	[thread overview]
Message-ID: <20190204142538.GN3532@calimero.vinschen.de> (raw)
In-Reply-To: <65068741-b05e-591f-1577-cab12650bee6@ssi-schaefer.com>

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

On Feb  4 14:19, Michael Haubenwallner wrote:
> On 2/3/19 12:19 PM, Corinna Vinschen wrote:
> > On Jan 31 20:48, Corinna Vinschen wrote:
> >> On Jan 31 09:47, Michael Haubenwallner wrote:
> >>> Hi Corinna,
> >>>
> >>> I'm missing that topic/forkables branch in the announcement - is that in?
> >>> https://cygwin.com/ml/cygwin-patches/2017-q1/msg00053.html
> >>
> >> No, it's not.  It hasn't been touched for almost two years so I forgot
> >> about it.
> >>
> >> Does it still apply to current mainline?  Will it still work correctly
> >> in conjunction with the Windows 10 1709/1803/1809 changes in terms of
> >> deleting and renaming files?
> 
> Are these changes available in Windows Server 2016 as well?

No, 2016 is equivalent to W10 1607.  You need 2019 which is equivalent
to W10 1809.

> >> More importantly, I'm not confident to maintain this code alone since it
> >> won't be used most of the time and it adds a heck of complexity to
> >> handle a border case.  Will you be available to maintain this code for
> >> the forseeable future?  If not, the code won't go in, sorry.
> 
> Actually I've maintained these patches while waiting for Cygwin 3 already:
> https://dev.gentoo.org/~haubi/cygwin-gentoo/x86_64/
> 
> Because we (the company) really need these patches, there will be someone
> around to fix any breakage, and for 2019 it's confirmed to be myself.

Ok.  I might have another potential user for these changes, so there
is apparently some demand.

> > I rebased the topic/forkable branch on top of master.  There were only
> > some minor conflicts which I have fixed correctly I hope.  Please give
> > it a thorough try.
> 
> For Gentoo Prefix we recently have set up CI builds in Azure for Linux.
> Are you aware of Windows+Cygwin build pipelines to be possible in Azure?

Nope, I'm a cloud refusenik ;)

Are you going to test the patched branch?


Thanks,
Corinna

-- 
Corinna Vinschen
Cygwin Maintainer

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

  reply	other threads:[~2019-02-04 14:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-30 21:23 Corinna Vinschen
2019-01-31  8:47 ` Michael Haubenwallner
2019-01-31 19:48   ` Corinna Vinschen
2019-02-03 11:19     ` Corinna Vinschen
2019-02-04 13:20       ` Michael Haubenwallner
2019-02-04 14:25         ` Corinna Vinschen [this message]
2019-02-05  8:42           ` Michael Haubenwallner
2019-02-05  9:45             ` Corinna Vinschen
2019-02-05 11:31               ` Michael Haubenwallner
2019-02-05 11:57                 ` Corinna Vinschen
2019-02-06 14:28       ` Michael Haubenwallner
2019-02-06 16:20         ` Corinna Vinschen
2019-02-06 16:34           ` Corinna Vinschen
2019-02-07  7:07             ` Michael Haubenwallner
2019-02-06 19:20           ` Andrey Repin
2019-02-07  8:32             ` Michael Haubenwallner

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=20190204142538.GN3532@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).