From: Arjun Shankar <arjun@redhat.com>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>,
GLIBC Devel <libc-alpha@sourceware.org>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
cltang@codesourcery.com, Carlos O'Donell <carlos@redhat.com>
Subject: Re: 2.31: glibc master is now kinda, sorta, frozen
Date: Mon, 06 Jan 2020 17:18:39 +0100 [thread overview]
Message-ID: <2d573c17c8bdcc8273e789261542df1b4533b59d.camel@redhat.com> (raw)
In-Reply-To: <c590370f-f0b0-e653-1cc1-89183a802011@gotplt.org>
Hi Siddhesh,
> - iconv: rewrite option parsing
> https://sourceware.org/ml/libc-alpha/2019-12/msg00613.html
>
> Arjun, how's this going? I see a v2 but no reviews. I'll review this
> on Thursday if nobody gets to it by then.
Florian has reviewed earlier versions of it with me, and it has two tests
which exercise the front end. Given this, I feel pretty confident about the
patch, overall.
I'm just waiting for reviews to come in on libc-alpha, and then I'll get to
work on a follow-up or check-in depending on the response(s). Carlos is
planning on reviewing it, so I should have some feedback soon. Of course,
I'll be happy to have your review if you have time to spare.
Cheers,
Arjun
next prev parent reply other threads:[~2020-01-06 16:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-31 16:29 2.31: glibc master is now kinda, sorta, frozen Siddhesh Poyarekar
2019-12-31 16:53 ` Adhemerval Zanella
2019-12-31 16:59 ` Adhemerval Zanella
2019-12-31 17:05 ` Rafal Luzynski
2020-01-06 15:41 ` Chung-Lin Tang
2020-01-06 15:46 ` Siddhesh Poyarekar
2020-01-07 9:07 ` Chung-Lin Tang
2020-01-07 22:15 ` Carlos O'Donell
2020-01-06 16:18 ` Arjun Shankar [this message]
2020-01-06 16:22 ` Siddhesh Poyarekar
2020-01-06 18:08 ` Arjun Shankar
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2d573c17c8bdcc8273e789261542df1b4533b59d.camel@redhat.com \
--to=arjun@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=cltang@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@gotplt.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).