From: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: tools@linux.kernel.org, users@linux.kernel.org
Subject: Re: [kernel.org users] b4 v0.3.4 released
Date: Wed, 25 Mar 2020 11:26:28 -0400 [thread overview]
Message-ID: <20200325152628.aju6peocay56ngdi@chatter.i7.local> (raw)
In-Reply-To: <CAHmME9os=HxxxqWHp9nM6ggDdkqwpa6gOpTTAG68gamR3NtWaA@mail.gmail.com>
On Tue, Mar 24, 2020 at 08:11:10PM -0600, Jason A. Donenfeld wrote:
> Hi Konstantin,
>
> Still not a fan at all of the attestation stuff
But look how pretty it looks!
https://mricon.com/misc/attestation.png
Would people like it better if I added emojis? :)
https://mricon.com/misc/attestation-with-feeling.png
(Just kidding. I know that not everyone is interested in patch-level
signatures, but seeing as we don't have *any* other mechanism of doing
end-to-end attestation for mailed patches at this time, I wanted to at
least take a stab at it and offer something usable and behind-the-scenes
enough not to annoy the heck out of everyone.)
> , but the lore
> integration is a great convenience. Thanks for this great tool. I've
> packaged it up for Gentoo:
>
> https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8374a4402f40ad1ff3613e281db5bb897708fcea
Nice. I've been holding off on doing the same for Fedora until b4 sees a
bit less churn. Perhaps in another week or so once the 0.3.y branch
stabilizes.
> Will you continue to send release announcements here, or should I set
> up a notifier through other means?
I will always send announcements to tools@linux.kernel.org at least, and
major feature additions will always be announced on the users list.
> I'm curious to learn: where did this name "b4" come from? Is it like
> the millennial meme phrase "inb4" being a deconstruction of "inbox"
> for a postmodern command line work of art?
Nothing that clever. I'm following the Trek theme started by V'ger:
The name "b4" was chosen for ease of typing and because B-4 was the
precursor to Lore and Data in the Star Trek universe.
-K
next prev parent reply other threads:[~2020-03-25 15:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 22:20 b4 v0.3.4 released Konstantin Ryabitsev
2020-03-25 2:11 ` [kernel.org users] " Jason A. Donenfeld
2020-03-25 2:19 ` Jason A. Donenfeld
2020-03-25 15:05 ` Konstantin Ryabitsev
2020-03-25 15:26 ` Konstantin Ryabitsev [this message]
2020-03-26 16:04 ` Rob Herring
2020-03-26 16:11 ` Rob Herring
2020-03-26 16:16 ` Konstantin Ryabitsev
2020-03-26 16:27 ` James Bottomley
2020-03-26 16:31 ` Geert Uytterhoeven
[not found] ` <15FFE6D3B979AF4C.32445@linux.kernel.org>
2020-03-26 16:32 ` Konstantin Ryabitsev
2020-03-26 20:18 ` Jason A. Donenfeld
2020-03-27 18:15 ` Konstantin Ryabitsev
2020-04-06 21:53 ` Konstantin Ryabitsev
2020-09-22 22:17 ` Rob Herring
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=20200325152628.aju6peocay56ngdi@chatter.i7.local \
--to=konstantin@linuxfoundation.org \
--cc=Jason@zx2c4.com \
--cc=tools@linux.kernel.org \
--cc=users@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).