Linux maintainer tooling and workflows
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Saurav Girepunje <saurav.girepunje@gmail.com>, tools@linux.kernel.org
Subject: b4 and lore and '/' in a message id
Date: Tue, 7 Sep 2021 08:39:50 +0200	[thread overview]
Message-ID: <YTcJNrbjTVMXCQUG@kroah.com> (raw)

I've run into problems with a specific user that happens to send patches
out with a '/' in the message id field.

I think this is a valid thing, but b4 and lore don't seem to handle this
very well.

Here's their latest patch:

$ b4 am YTRuXTu/kePBDwAF@user
Looking up https://lore.kernel.org/r/YTRuXTu%2FkePBDwAF%40user
That message-id is not known.

And yes, if you go to the above link, it is not found.

But, if you go to 'all' it is found:
	https://lore.kernel.org/all/YTRuXTu%2FkePBDwAF@user

Any hints on what to do here?

Note, this is the second time this has happened.  First time I wrongly
blamed the developer that they submitted the patch incorrectly, this
time they graciously pointed out that they had sent it correctly,
something was wrong with my side :)

Saurav, how are you sending these patches out, using 'git send-email' or
something else?  What is generating that message id?

thanks,

greg k-h

             reply	other threads:[~2021-09-07  6:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-07  6:39 Greg KH [this message]
2021-09-07 14:31 ` b4 and lore and '/' in a message id Konstantin Ryabitsev
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=YTcJNrbjTVMXCQUG@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=konstantin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox