From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.9.0-0.2
Date: Fri, 01 Sep 2017 13:05:00 -0000 [thread overview]
Message-ID: <20170901130534.GJ14109@calimero.vinschen.de> (raw)
In-Reply-To: <20170901122310.GF14109@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 1526 bytes --]
On Sep 1 14:23, Corinna Vinschen wrote:
> On Sep 1 11:44, Thomas Wolff wrote:
> > Am 30.08.2017 um 17:13 schrieb Corinna Vinschen:
> > > Hi folks,
> > >
> > >
> > > I uploaded a new Cygwin test release 2.9.0-0.2
> > >
> > > I'm planning for a release next week. Please test.
> > >
> > > ...
> > Any chance to get the wcwidth update into the next release? I've submitted a
> > reworked patch meanwhile to the newlib mailing list (for both string/wcwidth
> > and ctype/{is,to}w*) but no response there yet. If there is no agreement yet
> > how to proceed with the ctype functions, could we still update only the
> > wcwidth part already?
>
> I forgot to reply, sorry. I'm still irritated why you don't just
> simply send the patches as a git patch series. Create the set with
> git format-patch and send it to the newlib list with git send-email.
> No problems with patch size and mailbox limits and especially no
> external ZIP fgile nobody ever reviews.
Apart from that, I'm not really confident to push this patch for 2.9.0
on such short notice. We should leave some time for testing before
releasing it.
The problem is that I'm unavailable for about 4 weeks after the 2.9.0
release. Having said that, we can certainly apply the patch, but
only release it with 2.9.1 or 2.10.0, whatever we call the next one.
Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2017-09-01 13:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 15:32 Corinna Vinschen
2017-09-01 9:44 ` Thomas Wolff
2017-09-01 12:23 ` Corinna Vinschen
2017-09-01 13:05 ` 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=20170901130534.GJ14109@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).