[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#22044: 24.4; url-expand.el and url-parse.el not conforming to RFC 39
From: |
Alain Schneble |
Subject: |
bug#22044: 24.4; url-expand.el and url-parse.el not conforming to RFC 3986 |
Date: |
Sat, 26 Dec 2015 11:51:09 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.4 (windows-nt) |
John Wiegley <jwiegley@gmail.com> writes:
>>>>>> Alain Schneble <a.s@realize.ch> writes:
>
>> Thanks, great! I see nothing against backporting it to Emacs 25.1. But I
>> must be honest, I'm pretty new to Emacs and its hard for me to judge the
>> risks of doing so.
>
> At this point mainly ask yourself:
>
> 1. Would the change require new, or change existing, documentation or APIs?
> If so, it should go to master.
The bugfix does not change any public interface. And the documented
behavior is expected to remain the same.
> 2. If it corrects existing behavior, refines that behavior, or removes a
> stumbling block, it should go to emacs-25.
It clearly corrects existing behavior and adds a bunch of new test
cases. From that point of view, it shoud go to emacs-25.
> The length of time it takes to get emacs-25 fully ready should not be seen as
> an opening for "features that could get ready during that time". I haven't
> seen any attempts to commit such features, I just wanted to make this one
> point clear.
I see your point - thanks for clarifying this. But as stated above, I
don't think it falls into this category of changes.
Thanks!
Alain
- bug#22044: 24.4; url-expand.el and url-parse.el not conforming to RFC 3986, (continued)
- bug#22044: 24.4; url-expand.el and url-parse.el not conforming to RFC 3986, Eli Zaretskii, 2015/12/25
- bug#22044: 24.4; url-expand.el and url-parse.el not conforming to RFC 3986, Lars Ingebrigtsen, 2015/12/25
- bug#22044: 24.4; url-expand.el and url-parse.el not conforming to RFC 3986, Alain Schneble, 2015/12/25
- bug#22044: 24.4; url-expand.el and url-parse.el not conforming to RFC 3986, Lars Ingebrigtsen, 2015/12/25
- bug#22044: 24.4; url-expand.el and url-parse.el not conforming to RFC 3986, Alain Schneble, 2015/12/25
- bug#22044: 24.4; url-expand.el and url-parse.el not conforming to RFC 3986, Alain Schneble, 2015/12/25
- bug#22044: 24.4; url-expand.el and url-parse.el not conforming to RFC 3986, Lars Ingebrigtsen, 2015/12/25
- bug#22044: 24.4; url-expand.el and url-parse.el not conforming to RFC 3986, Alain Schneble, 2015/12/25
- bug#22044: 24.4; url-expand.el and url-parse.el not conforming to RFC 3986, John Wiegley, 2015/12/25
- bug#22044: 24.4; url-expand.el and url-parse.el not conforming to RFC 3986,
Alain Schneble <=
- bug#22044: 24.4; url-expand.el and url-parse.el not conforming to RFC 3986, Lars Ingebrigtsen, 2015/12/25
- bug#22044: 24.4; url-expand.el and url-parse.el not conforming to RFC 3986, Eli Zaretskii, 2015/12/26
- bug#22044: 24.4; url-expand.el and url-parse.el not conforming to RFC 3986, Lars Ingebrigtsen, 2015/12/26
- bug#22044: 24.4; url-expand.el and url-parse.el not conforming to RFC 3986, Eli Zaretskii, 2015/12/26