public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Shuah Khan <shuahkhan@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	postmaster@vger.kernel.org
Subject: Re: kernel mailing list permalinks
Date: Tue, 06 Aug 2013 14:23:36 -0700	[thread overview]
Message-ID: <52016958.70005@zytor.com> (raw)
In-Reply-To: <CAErSpo7z7b-i7qENa9q+8jLmsV=EFiykBy5wU1AE3eAMG1MKUA@mail.gmail.com>

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.
> 
> Ooh, thanks.  I wasn't aware of that, and I've certainly constructed
> links that are semi-broken because of this issue.  Having the
> permalink in the message footer would avoid that problem.
> 
> I don't know what it would take to implement this.  Escaping special
> characters makes it not quite as trivial as I thought it might be.
> 

Part of me wonders if we could/should make the bouncer recognize that a
space character is not a valid part of a Message-ID (I think) and change
it back into a +.

A quoted Message-ID might be weird as heck, but one rarely if ever see
them, I don't know if they are even legal.

	-hpa



  parent reply	other threads:[~2013-08-06 21:23 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 [this message]
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
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=52016958.70005@zytor.com \
    --to=hpa@zytor.com \
    --cc=bhelgaas@google.com \
    --cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox