From: "H. Peter Anvin" <hpa@zytor.com>
To: Joe Perches <joe@perches.com>
Cc: Anders Larsen <al@alarsen.net>,
Bjorn Helgaas <bhelgaas@google.com>,
Shuah Khan <shuahkhan@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
postmaster@vger.kernel.org,
Konstantin Ryabitsev <mricon@kernel.org>
Subject: Re: kernel mailing list permalinks
Date: Tue, 06 Aug 2013 20:39:57 -0700 [thread overview]
Message-ID: <5201C18D.2030907@zytor.com> (raw)
In-Reply-To: <1375830937.2424.41.camel@joe-AO722>
On 08/06/2013 04:15 PM, Joe Perches wrote:
> On Tue, 2013-08-06 at 16:05 -0700, H. Peter Anvin wrote:
>> On 08/06/2013 02:55 PM, Anders Larsen wrote:
>>> On 2013-08-06 23:23, H. Peter Anvin wrote:
>>>> On 08/06/2013 02:11 PM, Bjorn Helgaas wrote:
>>>>>>
>>>>>> The above link is also a good example of subtleness: + in a URL
>>>> means a
>>>>>> space character, it has to be escaped as %2B. Particularly a
>>>> problem in
>>>>>> gmail message-ids.
>>>
>>> the link in question works just fine without escaping the +; the + only
>>> has to be escaped in then query component of a URL, not in the path
>>> component where it is just another valid character - and the link in
>>> question did not contain any query component.
>>>
>>> (see RFC 3986 sections 3.3 and 3.4)
>
> Rather than relying on third party links,
> it'd be nice if vger was the archive too.
>
We probably should archive the contents, but it really doesn't seem to
matter if we outsource displaying it, does it?
-hpa
next prev parent reply other threads:[~2013-08-07 3:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 21:04 kernel mailing list permalinks Bjorn Helgaas
2013-08-02 21:36 ` Shuah Khan
2013-08-02 21:38 ` H. Peter Anvin
2013-08-06 21:11 ` Bjorn Helgaas
2013-08-06 21:15 ` H. Peter Anvin
2013-08-06 21:23 ` H. Peter Anvin
2013-08-06 21:55 ` Anders Larsen
2013-08-06 23:05 ` H. Peter Anvin
2013-08-06 23:15 ` Joe Perches
2013-08-07 3:39 ` H. Peter Anvin [this message]
2013-08-07 3:44 ` Joe Perches
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=5201C18D.2030907@zytor.com \
--to=hpa@zytor.com \
--cc=al@alarsen.net \
--cc=bhelgaas@google.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mricon@kernel.org \
--cc=postmaster@vger.kernel.org \
--cc=shuahkhan@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.