From: Zack Weinberg <zackw@panix.com>
To: Rafal Luzynski <digitalfreak@lingonborough.com>
Cc: TAMUKI Shoichi <tamuki@linet.gr.jp>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH v6 2/2] strftime: Pass the additional flags from "%EY" to "%Ey" [BZ #23758]
Date: Thu, 17 Jan 2019 21:32:25 -0500 [thread overview]
Message-ID: <CAKCAbMhFQs7vHuanc46-OwaHWXvZWNOeDAmu9UtxXTfkyCES+A@mail.gmail.com> (raw)
In-Reply-To: <184032555.404911.1547751249485@poczta.nazwa.pl>
On Thu, Jan 17, 2019 at 1:55 PM Rafal Luzynski
<digitalfreak@lingonborough.com> wrote:
> 16.01.2019 17:17 Zack Weinberg <zackw@panix.com> wrote:
> > (It seems to me that this extension ought to be generalized to all of
> > the "macro" formats (%c, %D, %F, %r, %R, %T, %x, %X, %Ec, %Ex, %EX),
> > and to all format flags and field widths, but that would be a separate
> > patch and not appropriate for 2.29 at this point.)
>
> This may be too ambiguous and therefore impossible to implement.
Yeah, you may be right there. It was just an idea.
> > | * As a GNU extension, the '-' and '_' flags can now be applied to '%EY'
> > | to control how the year number is formatted; they have the same effect
> > | that they would on %Ey.
>
> "they would" or "they would have"?
My ear says an additional "have" is not necessary, but feel free to
add it if it sounds better to you that way.
> Also, shouldn't all format specifiers be consequently quoted, like "%EY"
> and "%Ey"? I don't mind single quotes, especially for the flags, I just
> think that %Ey (without any quotes) may not be absolutely clear.
This is NEWS, right? In the manual it should be @code{} and no quotes
for all of them, IIRC, but yes, let's add quotes around %Ey. It
doesn't matter to me whether they are single or double quotes.
zw
prev parent reply other threads:[~2019-01-18 2:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 4:47 [PATCH v6 0/2] strftime: Improve the width of alternative representation for year [BZ #23758] TAMUKI Shoichi
2019-01-11 4:49 ` [PATCH v6 1/2] strftime: Set the default width of "%Ey" to 2 " TAMUKI Shoichi
2019-01-16 16:17 ` Zack Weinberg
2019-01-17 6:27 ` TAMUKI Shoichi
2019-01-17 17:56 ` Rafal Luzynski
2019-01-18 2:45 ` Zack Weinberg
2019-01-18 13:59 ` TAMUKI Shoichi
2019-01-18 18:35 ` Rafal Luzynski
2019-01-18 13:56 ` TAMUKI Shoichi
2019-01-18 18:44 ` Rafal Luzynski
2019-01-19 3:51 ` TAMUKI Shoichi
2019-01-19 17:08 ` Zack Weinberg
2019-01-19 21:42 ` Rafal Luzynski
2019-01-11 4:52 ` [PATCH v6 2/2] strftime: Pass the additional flags from "%EY" to "%Ey" " TAMUKI Shoichi
2019-01-16 16:17 ` Zack Weinberg
2019-01-17 18:54 ` Rafal Luzynski
2019-01-18 2:32 ` Zack Weinberg [this message]
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=CAKCAbMhFQs7vHuanc46-OwaHWXvZWNOeDAmu9UtxXTfkyCES+A@mail.gmail.com \
--to=zackw@panix.com \
--cc=digitalfreak@lingonborough.com \
--cc=libc-alpha@sourceware.org \
--cc=tamuki@linet.gr.jp \
/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).