From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>,
GLIBC Devel <libc-alpha@sourceware.org>
Cc: cltang@codesourcery.com, Carlos O'Donell <carlos@redhat.com>,
arjun@redhat.com
Subject: Re: 2.31: glibc master is now kinda, sorta, frozen
Date: Tue, 31 Dec 2019 13:59:10 -0300 [thread overview]
Message-ID: <30ca5135-13b3-bfb7-3ae3-64a9993fb872@linaro.org> (raw)
In-Reply-To: <4f7aabd7-29e9-2dd1-1fca-634b57d2f6a4@linaro.org>
On 31/12/2019 13:53, Adhemerval Zanella wrote:
>
>
> On 31/12/2019 13:29, Siddhesh Poyarekar wrote:
>>
>> - vDSO refactor and fixes
>> https://sourceware.org/ml/libc-alpha/2019-12/msg00597.html
>>
>> Adhemerval, I see some reviews and change requests. Are you waiting for
>> reviews on the rest of your patches or do you intend to post a v3
>> patchset? I can help with reviews on Thursday if nobody gets to it by then.
>
> I will check the review already done and send updated versions, thanks
> for checking on it.
Hi Siddhesh,
The latest version [1] received some sparse review that I fixed locally
and I don't think it is worth to send an updated version (I can if you
prefer).
[1] https://sourceware.org/ml/libc-alpha/2019-12/msg00597.html
next prev parent reply other threads:[~2019-12-31 16:59 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 [this message]
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
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=30ca5135-13b3-bfb7-3ae3-64a9993fb872@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=arjun@redhat.com \
--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).