get-lore-inbox is now b4

get-lore-inbox is now b4

[Konstantin Ryabitsev]

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

Hi, all:

While working on patch attestation stuff, it became clear to me that it 
would be much easier if get-lore-mbox was an actual python project 
instead of a standalone script. As a bonus, such change would also make 
the tool easier to install, upgrade and package. So, say goodbye to 
get-lore-mbox and say hello to b4.

Installing:

  python3 -m pip install --user b4

Upgrading:

  python3 -m pip install --user --upgrade b4

(Just using "pip" instead of "python3 -m pip" will probably work, too.)

If your ~/.local/bin is not in your PATH yet, you can either set a 
symlink to b4 there from your usual PATH, use an alias, or add 
~/.local/bin to your path.

At version 0.3.1, b4 is pretty much get-lore-mbox version 0.2.16 plus 
the "Fixes" tweak from this morning (and plus the whole attestation 
stuff).  

You will notice that b4 is very much flag-compatible with get-lore-mbox:

old:

  get-lore-mbox -a [msgid] [flags]

new:

  b4 am [msgid] [same flags]

You can easily see all flags by running:

  b4 am --help

The biggest visual change for you would become obvious if you're 
grabbing patches that provide attestation, e.g.:

---
$ b4 am -o/tmp 20200313231252.64999-1-keescook@chromium.org
Looking up https://lore.kernel.org/r/20200313231252.64999-1-keescook@chromium.org
Grabbing thread from lore.kernel.org
Analyzing 3 messages in the thread
---
Writing /tmp/v2_20200313_keescook_chromium_org.mbx
  [✓] [PATCH v2 1/2] selftests/harness: Move test child waiting logic
  [✓] [PATCH v2 2/2] selftests/harness: Handle timeouts cleanly
  ---
  [✓] Attestation-by: Kees Cook <keescook@chromium.org> (pgp: 8972F4DFDC6DC026)
---
Total patches: 2
---
Cover: /tmp/v2_20200313_keescook_chromium_org.cover
 Link: https://lore.kernel.org/r/20200313231252.64999-1-keescook@chromium.org
 Base: not found, sorry
       git checkout -b v2_20200313_keescook_chromium_org master
       git am /tmp/v2_20200313_keescook_chromium_org.mbx
---

Attestation is still an experimental feature, so if you find that it 
breaks something for you, you can turn it off entirely by adding the 
following to your ~/.gitconfig:

[b4]
  attestation-policy = off

The default policy is "check", which will look for an attestation 
document but will not give any warnings if it doesn't find anything.

If you are interested in playing with patch attestation, it is very easy 
to get started:

1. find a bunch of patches you sent off recently, preferably those 
   prepared by "git-format-patch"
2. run "b4 attest *.patch"

This will submit the attestation message to mail.kernel.org:587. If it 
is unable to do so, it will write the attestation message out into
cwd. See more options with: b4 attest --help.

Finally, there's a new mailing list for discussing b4 and similar 
utilities:

tools@linux.kernel.org

Please send future bug reports or other problems there instead of to 
users@ (though you're welcome to do both).

Best regards,
Konstantin

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