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: Re: b4 and lore and '/' in a message id
Date: Wed, 8 Sep 2021 15:49:17 +0200	[thread overview]
Message-ID: <YTi/XYzSLo3gNne9@kroah.com> (raw)
In-Reply-To: <20210908131158.it5lhuxyc7arw4uv@meerkat.local>

On Wed, Sep 08, 2021 at 09:11:58AM -0400, Konstantin Ryabitsev wrote:
> 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.
> > 
> > I think this is a valid thing, but b4 and lore don't seem to handle this
> > very well.
> 
> The latest public-inbox version allows us to do the right thing here, so
> things work as expected now:
> 
> 	$ b4 am YTRuXTu/kePBDwAF@user
> 	Looking up https://lore.kernel.org/r/YTRuXTu%2FkePBDwAF%40user
> 	Analyzing 5 messages in the thread
> 	Checking attestation on all messages, may take a moment...
> 	---
> 	  ✓ [PATCH] staging: r8188eu: include: remove duplicate declaration.
> 	  ---
> 	  ✓ Signed: DKIM/gmail.com
> 	---
> 	Total patches: 1
> 	---
> 	 Link: https://lore.kernel.org/r/YTRuXTu/kePBDwAF@user
> 	 Base: applies clean to current tree
> 		   git am ./20210905_saurav_girepunje_staging_r8188eu_include_remove_duplicate_declaration.mbx
> 
> Best regards,
> -K

Wonderful, thank you!

greg k-h

      reply	other threads:[~2021-09-08 13:49 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
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 [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=YTi/XYzSLo3gNne9@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