tools.linux.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Mark Brown" <broonie@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org
Subject: b4 message ID shortening
Date: Mon, 23 Mar 2020 12:54:56 +0000	[thread overview]
Message-ID: <20200323125456.GC4948@sirena.org.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 896 bytes --]

When generating filenames to save messages b4 am looks like it truncates
the message ID to generate the default filename (or possibly uses a
portion of the date now I think about it, I didn't read the code).  For
example

   https://lore.kernel.org/r/20200320232515.GA24800@embeddedor.com

results in a mailbox

   20200320_gustavo_embeddedor_com.mbx

which is all well and good except if you also try to save:

   https://lore.kernel.org/r/20200320232556.GA24989@embeddedor.com

it generates the same filename and silently overwrites the first
mailbox.  Using b4 mbox avoids this as it generates files using the full
message ID such as

   20200320232515.GA24800@embeddedor.com.t.mbx-thread

which avoids collisions.

FWIW my workflow is currently to save a bunch of mailboxes into a
directory then throw them at a script to do some testing & apply them if
that works.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 499 bytes --]

             reply	other threads:[~2020-03-23 12:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-23 12:54 Mark Brown [this message]
2020-03-23 16:38 ` b4 message ID shortening Konstantin Ryabitsev
2020-03-23 17:05   ` Mark Brown
2020-03-23 18:04     ` Konstantin Ryabitsev
2020-03-23 18:50       ` Mark Brown

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=20200323125456.GC4948@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=konstantin@linuxfoundation.org \
    --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).