tools.linux.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Kyle Meyer <kyle@kyleam.com>
Cc: Morten Linderud <foxboron@archlinux.org>, tools@linux.kernel.org
Subject: Re: b4: Ensure we read threadfile for message-id
Date: Fri, 14 May 2021 16:55:37 -0400	[thread overview]
Message-ID: <20210514205537.s7eofbqkbjziofbk@meerkat.local> (raw)
In-Reply-To: <87im4fi55o.fsf@kyleam.com>

On Wed, Apr 21, 2021 at 07:33:55PM -0400, Kyle Meyer wrote:
> I haven't tried, but it looks like you could update the get_msgid() call
> in mbox_to_am() to use mboxfile.
> 
> Another approach would be to avoid collecting the msgid more than once
> (something like below).

This is indeed a better approach, so I used it in the latest dev commit.
Thanks to both of you.

-K

      reply	other threads:[~2021-05-14 20:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-21 20:29 b4: Ensure we read threadfile for message-id Morten Linderud
2021-04-21 23:33 ` Kyle Meyer
2021-05-14 20:55   ` Konstantin Ryabitsev [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=20210514205537.s7eofbqkbjziofbk@meerkat.local \
    --to=konstantin@linuxfoundation.org \
    --cc=foxboron@archlinux.org \
    --cc=kyle@kyleam.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;
as well as URLs for NNTP newsgroup(s).