public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
	Benno Schulenberg <coordinator@translationproject.org>,
	libc-alpha@sourceware.org, Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: libc-2.25.90.pot
Date: Thu, 20 Jul 2017 11:17:00 -0000	[thread overview]
Message-ID: <fb5dc1d1-37b5-b329-58a9-4bea85ff8d10@gotplt.org> (raw)
In-Reply-To: <f1f4631f-3e71-2645-daef-f180da38c8db@gotplt.org>

On Wednesday 19 July 2017 07:19 PM, Siddhesh Poyarekar wrote:
> On Wednesday 19 July 2017 06:58 PM, Adhemerval Zanella wrote:
>> I think for glibc, since we support C99 intmax_t printf format, we can
>> just use %jd instead:
>>
>> 	* timezone/zic.c (PRIdLINENO): Remove macro.
>> 	(verror): Use %jd instead of PRIdLINENO.
> 
> Fine with me, but I'd like to hear from Joseph/Paul too if they have any
> context from the tz project that may make this a bad idea.

In the interest of unblocking the translation team, lets wait till
tomorrow and then commit if there are no objections.  The more I look at
the change the more it looks like future-proofing and not relevant to a
current problem.  If the future-proofing is necessary, we can get it
back in 2.26.90 in a way that does not break translation strings.

Siddhesh

  reply	other threads:[~2017-07-20 11:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8b9b4e60-f580-e56a-26bc-adb7192ba779@sourceware.org>
     [not found] ` <6e7f7602-3536-2edb-0cf4-e66a948fdb71@translationproject.org>
2017-07-18 17:08   ` libc-2.25.90.pot Benno Schulenberg
2017-07-18 19:02     ` libc-2.25.90.pot Adhemerval Zanella
2017-07-19  7:15       ` libc-2.25.90.pot Siddhesh Poyarekar
2017-07-19  7:33         ` libc-2.25.90.pot Benno Schulenberg
2017-07-19 13:28           ` libc-2.25.90.pot Adhemerval Zanella
2017-07-19 13:50             ` libc-2.25.90.pot Siddhesh Poyarekar
2017-07-20 11:17               ` Siddhesh Poyarekar [this message]
2017-07-20 12:52                 ` libc-2.25.90.pot Adhemerval Zanella
2017-07-20 14:57                   ` libc-2.25.90.pot Siddhesh Poyarekar
2017-07-20 19:41                     ` libc-2.25.90.pot Paul Eggert
2017-07-25 10:23                       ` libc-2.25.90.pot Siddhesh Poyarekar
     [not found]   ` <0961b9b1-b6b9-c0c9-bfe3-929ce522d7a8@sourceware.org>
2017-07-19  7:10     ` libc-2.25.90.pot Siddhesh Poyarekar

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=fb5dc1d1-37b5-b329-58a9-4bea85ff8d10@gotplt.org \
    --to=siddhesh@gotplt.org \
    --cc=adhemerval.zanella@linaro.org \
    --cc=coordinator@translationproject.org \
    --cc=eggert@cs.ucla.edu \
    --cc=libc-alpha@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).