From: Mark Wielaard <mark@klomp.org>
To: Noah Sanci <nsanci@redhat.com>
Cc: elfutils-devel@sourceware.org
Subject: Re: [Bug debuginfod/28034] %-escape url characters
Date: Thu, 22 Jul 2021 14:28:14 +0200 [thread overview]
Message-ID: <24d5603ba07066ec3d55266b33950eb812124f1e.camel@klomp.org> (raw)
In-Reply-To: <CAJXA7qiHxBxryT67msvo2e256LYj9syWKx=2LxFErZL81KDkQw@mail.gmail.com>
Hi Noah,
On Wed, 2021-07-21 at 14:18 -0400, Noah Sanci via Elfutils-devel wrote:
>
> > > +Note: the client should %-escape characters in /SOURCE/FILE that
> > > are not shown as "unreserved" in section 2.3 of RFC3986.
>
> Please read the new note just to ensure that it's reasonable, as my
> updated note specifies some characters that will be percent escaped.
> Otherwise fixed.
Yes, that looks good.
As do the alloc error checks and the test cleanups.
I'll push the minor fixed version you posted.
Thanks,
Mark
prev parent reply other threads:[~2021-07-22 12:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 14:53 Noah Sanci
2021-07-20 17:50 ` Mark Wielaard
2021-07-20 18:13 ` Frank Ch. Eigler
2021-07-20 19:08 ` Mark Wielaard
2021-07-21 18:18 ` Noah Sanci
2021-07-21 19:44 ` Noah Sanci
2021-07-22 12:29 ` Mark Wielaard
2021-07-22 12:28 ` Mark Wielaard [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=24d5603ba07066ec3d55266b33950eb812124f1e.camel@klomp.org \
--to=mark@klomp.org \
--cc=elfutils-devel@sourceware.org \
--cc=nsanci@redhat.com \
/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).