From: John Wiegley <jwiegley@gmail.com>
To: Alain Schneble <a.s@realize.ch>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 22044@debbugs.gnu.org
Subject: bug#22044: 24.4; url-expand.el and url-parse.el not conforming to RFC 3986
Date: Fri, 25 Dec 2015 16:51:03 -0800 [thread overview]
Message-ID: <m27fk2f2x4.fsf@newartisans.com> (raw)
In-Reply-To: <86fuyqnjl2.fsf@realize.ch> (Alain Schneble's message of "Sat, 26 Dec 2015 01:23:53 +0100")
>>>>> 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.
2. If it corrects existing behavior, refines that behavior, or removes a
stumbling block, it should 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.
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
next prev parent reply other threads:[~2015-12-26 0:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-28 21:53 bug#22044: 24.4; url-expand.el and url-parse.el not conforming to RFC 3986 Alain Schneble
2015-11-28 23:42 ` Alain Schneble
2015-12-25 18:01 ` Lars Ingebrigtsen
2015-12-25 19:45 ` Eli Zaretskii
2015-12-25 19:54 ` Lars Ingebrigtsen
2015-12-25 19:58 ` Lars Ingebrigtsen
2015-12-25 22:27 ` Alain Schneble
2015-12-25 22:39 ` Lars Ingebrigtsen
2015-12-25 22:48 ` Alain Schneble
2015-12-25 23:44 ` Alain Schneble
2015-12-25 23:51 ` Lars Ingebrigtsen
2015-12-26 0:23 ` Alain Schneble
2015-12-26 0:51 ` John Wiegley [this message]
2015-12-26 10:51 ` Alain Schneble
2015-12-26 1:06 ` Lars Ingebrigtsen
2015-12-26 10:12 ` Eli Zaretskii
2015-12-26 13:53 ` Lars Ingebrigtsen
2015-12-26 9:57 ` Eli Zaretskii
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=m27fk2f2x4.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=22044@debbugs.gnu.org \
--cc=a.s@realize.ch \
--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).