From: Corinna Vinschen <vinschen@redhat.com>
To: Gedare Bloom <gedare@rtems.org>
Cc: "newlib@sourceware.org" <newlib@sourceware.org>,
Joel Sherrill <joel.sherrill@oarcorp.com>
Subject: Re: Importing inttypes methods from FreeBSD
Date: Fri, 21 Jul 2017 19:31:00 -0000 [thread overview]
Message-ID: <20170721193106.GE20425@calimero.vinschen.de> (raw)
In-Reply-To: <CAC82fA2oQtRshCn6MutjEoQwKvvstn9j8uFX-E_3+aG3GFeGxw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1478 bytes --]
On Jul 21 11:42, Gedare Bloom wrote:
> On Thu, Jul 20, 2017 at 10:37 AM, Corinna Vinschen <vinschen@redhat.com> wrote:
> > Joel, please take an interest in Aditya's work in the first place.
> > *You* were the one who gave these tasks to Aditya, so *you* should be
> > the one guiding him and reviewing these patches, not me.
> > For any followup patches, I will not look into them unless you gave
> > your OK first.
> >
>
> Thank you for the helpful feedback, which is important to help new
> developers to understand how to work with an open source project. It
> usually takes Joel or myself a few days to a week to review patches. I
> understand completely if you would like to ignore the patches from our
> Google Summer of Code student since he is still learning and will
> inevitably make some mistakes. He started out with private emails, but
> I encouraged him to post to this mailing list in order to increase his
> visibility and learn how to better communicate with the community
> here. Meanwhile, he has sent me a new set of patches in private that
> look good. I hope he will feel comfortable to send them to the mailing
> list soon.
To clarify:
Patches should be sent to this list and then somebody of you guys should
review them *on this list*. Once done and you're OK with the patch, I'll
recheck the patches and either one of us will push them eventually.
Thanks,
Corinna
--
Corinna Vinschen
Cygwin Maintainer
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-07-21 19:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 21:40 Aditya Upadhyay
2017-07-19 9:34 ` Sebastian Huber
2017-07-19 10:16 ` Aditya Upadhyay
2017-07-19 10:58 ` Sebastian Huber
2017-07-19 12:28 ` Corinna Vinschen
2017-07-19 13:23 ` Aditya Upadhyay
2017-07-19 14:13 ` Craig Howland
2017-07-19 15:44 ` Corinna Vinschen
2017-07-19 17:00 ` Aditya Upadhyay
2017-07-20 8:25 ` Aditya Upadhyay
2017-07-20 14:37 ` Corinna Vinschen
2017-07-21 15:43 ` Gedare Bloom
2017-07-21 19:31 ` Corinna Vinschen [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-07-11 6:01 Aditya Upadhyay
2017-07-11 3:29 Aditya Upadhyay
2017-07-11 9:06 ` Corinna Vinschen
[not found] ` <CAMZxAxccBx9oDRiVE-mw5JEcKrLW4GKTdvg-dt+8bTHU=5j54w@mail.gmail.com>
2017-07-12 9:50 ` Aditya Upadhyay
2017-07-12 12:07 ` Corinna Vinschen
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=20170721193106.GE20425@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=gedare@rtems.org \
--cc=joel.sherrill@oarcorp.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).