From: Alain Schneble <a.s@realize.ch>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 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 23:27:07 +0100 [thread overview]
Message-ID: <86ziwytb9g.fsf@realize.ch> (raw)
In-Reply-To: <87twn6ti5x.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 25 Dec 2015 20:58:02 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
Hello Lars
> Alain Schneble <a.s@realize.ch> writes:
>
>> * test/automated/url-parse-tests.el: add tests covering url-generic-parse-url.
>> * test/automated/url-expand-tests.el: add tests covering url-expand-file-name.
>> * test/automated/url-parse.el (url-generic-parse-url): keep empty fragment
>> information in URL-struct.
>
> This is apparently a new top-level directory. Are these supposed to be
> in this directory, is is this an error?
When I created the patch, the new test directory layout (see 75336a2 -
Merge branch 'feature/standard-test-location') has not yet been merged
to master. I guess that these tests should now reside in test/lisp/url/
if we follow the new convention. Shall I create a new patch or will you
just move the files there?
Many thanks for looking into my changes.
Alain
next prev parent reply other threads:[~2015-12-25 22:27 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 [this message]
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
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=86ziwytb9g.fsf@realize.ch \
--to=a.s@realize.ch \
--cc=22044@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).