From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: Michael Haubenwallner <michael.haubenwallner@ssi-schaefer.com>
Cc: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST: Cygwin 3.0.0-0.7
Date: Mon, 11 Feb 2019 13:33:00 -0000 [thread overview]
Message-ID: <20190211133335.GC3718@calimero.vinschen.de> (raw)
In-Reply-To: <54a5ff3e-4d6a-de39-cc02-f2533072552e@ssi-schaefer.com>
[-- Attachment #1: Type: text/plain, Size: 962 bytes --]
On Feb 11 12:50, Michael Haubenwallner wrote:
>
>
> On 2/8/19 6:00 PM, Corinna Vinschen wrote:
> > On Feb 8 17:58, Corinna Vinschen wrote:
> >> On Feb 8 17:35, Michael Haubenwallner wrote:
> >>>
> >>> On 2/8/19 2:28 PM, Corinna Vinschen wrote:
> >>>>
> >>>> I pushed your forkable branch to master, btw. Would you mind to do the
> >>>> honors in the ;rease notes at cygwin/release/3.0 and doc/new-features.xml?
> >>>
> >>> Do you mean like this?
>
> >>
> >> It's not bad but for release notes it's rather long. Any chance to get
> >> a more compact text? Also, please add a "Cygwin: " prefix to the log
> >> message summary. I'd like to distinguish CYgwin-only changes from
> >> newlib changes.
> >
> > OTOH, if you want to extend the documentation, feel free...
>
> Another try, with polish to already available doc around the forkables.
Looks good, pushed.
Thanks,
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-02-11 13:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 15:24 Corinna Vinschen
2019-02-07 16:14 ` Michael Haubenwallner
2019-02-07 18:27 ` Corinna Vinschen
2019-02-08 6:46 ` Michael Haubenwallner
2019-02-08 11:32 ` Corinna Vinschen
2019-02-08 11:51 ` Michael Haubenwallner
2019-02-08 12:21 ` Corinna Vinschen
2019-02-08 12:23 ` Corinna Vinschen
2019-02-08 12:52 ` Michael Haubenwallner
2019-02-08 13:06 ` Corinna Vinschen
2019-02-08 13:28 ` Corinna Vinschen
2019-02-08 14:43 ` Michael Haubenwallner
2019-02-08 14:49 ` Corinna Vinschen
2019-02-08 16:18 ` Michael Haubenwallner
2019-02-08 16:50 ` Corinna Vinschen
2019-02-08 16:35 ` Michael Haubenwallner
2019-02-08 16:58 ` Corinna Vinschen
2019-02-08 17:00 ` Corinna Vinschen
2019-02-11 11:50 ` Michael Haubenwallner
2019-02-11 13:33 ` 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=20190211133335.GC3718@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
--cc=michael.haubenwallner@ssi-schaefer.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).