From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: [PATCH] Fix RTEMS ioctl() declaration
Date: Fri, 09 Jun 2017 13:36:00 -0000 [thread overview]
Message-ID: <20170609133642.GB26770@calimero.vinschen.de> (raw)
In-Reply-To: <cd0fa5f7-d1ff-f2a9-ef80-b5b8cc4c561d@embedded-brains.de>
[-- Attachment #1: Type: text/plain, Size: 553 bytes --]
On Jun 8 07:32, Sebastian Huber wrote:
> On 07/06/17 16:27, Corinna Vinschen wrote:
>
> > [...]
> > Ok. At this point I would have replied "please apply", but you
> > already did that. It's write *after* approval ;)
>
> Sorry for the rush.
>
> So, you are not particularly fond of having OS port maintainers in Newlib
> similar to GCC?
It's more about timing. From write-after-approval to writing w/o
approval in less than an hour? Talking about rushing things...
Corinna
--
Corinna Vinschen
Cygwin Maintainer
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2017-06-09 13:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 9:08 Sebastian Huber
2017-06-07 13:11 ` Corinna Vinschen
2017-06-07 13:14 ` Sebastian Huber
2017-06-07 14:27 ` Corinna Vinschen
2017-06-08 5:33 ` Sebastian Huber
2017-06-09 13:36 ` 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=20170609133642.GB26770@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=newlib@sourceware.org \
/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).