From: Andreas Politz <politza@hochschule-trier.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 14776@debbugs.gnu.org
Subject: bug#14776: 24.3.50; [PATCH] parse-time-string performance
Date: Sat, 06 Jul 2013 18:07:37 +0200 [thread overview]
Message-ID: <87obafr7sm.fsf@hochschule-trier.de> (raw)
In-Reply-To: <87r4fby95z.fsf@building.gnus.org> (Lars Ingebrigtsen's message of "Sat, 06 Jul 2013 17:56:08 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Andreas Politz <politza@hochschule-trier.de> writes:
>
>>> I see no reason to keep both the old 10x slower version and the new fast
>>> version.
>>
>> Except for non-mail related packages/users.
>
> Well, the old function is designed for parsing RFC822 Date headers...
That may be true, though there is no mentioning of it in the file. But
that may not the only context in which it is used. It accepts all kinds
of date formats, even without touching parse-time-rules.
-ap
next prev parent reply other threads:[~2013-07-06 16:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 1:21 bug#14776: 24.3.50; [PATCH] parse-time-string performance Andreas Politz
2013-07-03 1:27 ` Andreas Politz
2013-07-03 3:32 ` Glenn Morris
2013-07-03 3:34 ` Glenn Morris
2013-07-04 15:41 ` Andreas Politz
2013-07-04 18:41 ` Lars Magne Ingebrigtsen
2013-07-04 19:47 ` Andreas Politz
2013-07-04 20:31 ` Lars Magne Ingebrigtsen
2013-07-04 21:08 ` Andreas Politz
2013-07-04 21:15 ` Lars Magne Ingebrigtsen
[not found] ` <87hagaeztj.fsf@hochschule-trier.de>
2013-07-06 15:34 ` Lars Ingebrigtsen
2013-07-06 15:50 ` Andreas Politz
2013-07-06 15:56 ` Lars Ingebrigtsen
2013-07-06 16:07 ` Andreas Politz [this message]
2013-07-06 17:47 ` Andreas Politz
2013-07-08 14:51 ` Lars Magne Ingebrigtsen
2016-03-01 1:05 ` Lars Ingebrigtsen
2019-06-27 11:12 ` Lars Ingebrigtsen
2013-07-04 22:21 ` Andreas Politz
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87obafr7sm.fsf@hochschule-trier.de \
--to=politza@hochschule-trier.de \
--cc=14776@debbugs.gnu.org \
--cc=larsi@gnus.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).