public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Elmar Stellnberger <estellnb@elstel.org>,
	libc-alpha@sourceware.org, libc-maintainers@gnu.org
Subject: Re: time64 functions for glibc
Date: Wed, 23 Jun 2021 10:29:33 -0300	[thread overview]
Message-ID: <ce5aa5cb-f21e-2ac5-0222-6bce89c9928c@linaro.org> (raw)
In-Reply-To: <e7f97130-580a-07a1-ec1d-16b55bd8e9a5@cs.ucla.edu>



On 22/06/2021 18:41, Paul Eggert wrote:
> On 5/31/21 12:03 PM, Adhemerval Zanella wrote:
> 
>>> Proposed patch attached, relative to the azanella/y2038 branch.
>>
>> Thanks, the patch looks reasonable and I will add merge on the
>> patch that enable the y2038 symbols.
> 
> That documentation patch didn't make it into the master branch when the corresponding y2038 symbols did. OK to install that doc patch now? I've attached it to this email (this is relative to current master).

LGTM, thanks. Sorry, I missed the rebase to include it.

Reviewed-by: Adhemerval Zanella  <adhemerval.zanella@linaro.org>

  reply	other threads:[~2021-06-23 13:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-31 15:43 Elmar Stellnberger
2021-05-31 15:51 ` Paul Zimmermann
2021-05-31 16:01 ` Adhemerval Zanella
2021-05-31 18:46   ` Paul Eggert
2021-05-31 18:56     ` Florian Weimer
2021-05-31 19:08       ` Adhemerval Zanella
2021-05-31 19:16         ` Florian Weimer
2021-05-31 19:28           ` Adhemerval Zanella
2021-06-01 16:32             ` Elmar Stellnberger
2021-05-31 19:03     ` Adhemerval Zanella
2021-06-22 21:41       ` Paul Eggert
2021-06-23 13:29         ` Adhemerval Zanella [this message]
2021-06-23 16:59         ` Joseph Myers
2021-06-23 17:59           ` Paul Eggert
2021-06-24 17:37             ` Joseph Myers

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=ce5aa5cb-f21e-2ac5-0222-6bce89c9928c@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=eggert@cs.ucla.edu \
    --cc=estellnb@elstel.org \
    --cc=libc-alpha@sourceware.org \
    --cc=libc-maintainers@gnu.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).