This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Fwd: Accelerating Y2038 glibc fixes
- From: Zack Weinberg <zackw at panix dot com>
- To: GNU C Library <libc-alpha at sourceware dot org>
- Date: Fri, 9 Aug 2019 08:32:03 -0400
- Subject: Fwd: Accelerating Y2038 glibc fixes
- References: <20190712072103.D3DBC24003A@gemini.denx.de> <alpine.DEB.2.21.1907251934270.17883@digraph.polyomino.org.uk> <20190726123902.6f8813da@jawa> <CAKCAbMjvrgebp9qhbK3TiH3fNEx+Xg0B9tGgJv=iVjRwUKEdoQ@mail.gmail.com> <20190730160430.6b6f302e@jawa> <20190809092544.615385de@jawa> <CAKCAbMhOMQ9yTFpy+OQkDvZPPFf_fFn6oSxjvLTaUwC4jpPRag@mail.gmail.com>
[forwarding accidental off-list reply]
On Fri, Aug 9, 2019 at 3:26 AM Lukasz Majewski <lukma@denx.de> wrote:
> > > I haven’t been following the details of these patches super
> > > carefully, and I’m not sure I understand what _Joseph’s_ concerns
> > > with your writing is. However, I’m a native English speaker, I’ve
> > > read over the text in the patch at
> > > <https://patchwork.ozlabs.org/patch/1117100/>, I do think I
> > > understand the issues at a high level, and I do think the meaning
> > > of __ASSUME_TIME64_SYSCALLS could be explained more clearly. I’m
> > > prepared to work with you to come up with better wording
> >
> > Thanks for offering your help.
>
> Shall I provide more input to this issue?
Not yet. Your answers to the questions I asked were helpful, but they
made it clear that I need to read over your entire patch set before I
can respond. I did not have time to do that in the past couple weeks
because I've been busy with my actual job. I hope to do it early next
week. Thank you for your patience.
zw