All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Saurav Girepunje <saurav.girepunje@gmail.com>, tools@linux.kernel.org
Subject: Re: b4 and lore and '/' in a message id
Date: Tue, 7 Sep 2021 10:31:07 -0400	[thread overview]
Message-ID: <20210907143107.dlygwnyl3v5w345m@meerkat.local> (raw)
In-Reply-To: <YTcJNrbjTVMXCQUG@kroah.com>

On Tue, Sep 07, 2021 at 08:39:50AM +0200, Greg KH wrote:
> I've run into problems with a specific user that happens to send patches
> out with a '/' in the message id field.

There's some interesting interaction between nginx, varnish, and public-inbox
that results in this behaviour. There is a way to solve it, but I don't like
the approach, so I'm going to work with upstream to see what my options are.

-K


  reply	other threads:[~2021-09-07 14:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-07  6:39 b4 and lore and '/' in a message id Greg KH
2021-09-07 14:31 ` Konstantin Ryabitsev [this message]
2021-09-07 14:36   ` Greg KH
2021-09-08  9:46 ` Saurav Girepunje
2021-09-08  9:54   ` Greg KH
2021-09-08 13:11 ` Konstantin Ryabitsev
2021-09-08 13:49   ` Greg KH

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=20210907143107.dlygwnyl3v5w345m@meerkat.local \
    --to=konstantin@linuxfoundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=saurav.girepunje@gmail.com \
    --cc=tools@linux.kernel.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. 
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.