From: Paul Eggert <eggert@cs.ucla.edu>
To: Assaf Gordon <assafgordon@gmail.com>,
Alex Eulenberg <alex@rent-a-mind.com>,
bug-gnulib@gnu.org
Subject: Re: [PATCH] ISO 8601 basic format and decimal hours, minutes
Date: Sun, 7 Apr 2019 22:05:52 -0700 [thread overview]
Message-ID: <6dacc9e4-61ea-7789-8d64-042316b3a90c@cs.ucla.edu> (raw)
In-Reply-To: <8e527169-6d2b-805b-157f-893f78d324ab@gmail.com>
Assaf Gordon wrote:
> Adding new accepted formats is good,
> but rejecting (or changing the meaning of) currently-accepted formats
> is a much more problematic decision due to breaking existing programs.
>
> I think that before continuing, it should be discussed and decided
> whether this is acceptable or not (Paul, Jim?).
I'd rather not reject existing valid input unless there's a good reason. Is
there one? I didn't see one in the original proposal (admittedly I didn't read
it word for word).
next prev parent reply other threads:[~2019-04-08 5:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 4:00 [PATCH] ISO 8601 basic format and decimal hours, minutes Alex Eulenberg
2019-04-07 3:26 ` Alex Eulenberg
2019-04-07 7:20 ` Assaf Gordon
2019-04-08 5:05 ` Paul Eggert [this message]
2020-03-23 0:07 ` Alex Eulenberg
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://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6dacc9e4-61ea-7789-8d64-042316b3a90c@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=alex@rent-a-mind.com \
--cc=assafgordon@gmail.com \
--cc=bug-gnulib@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).