b4 auto-thankanator landed in master

["Konstantin Ryabitsev" <konstantin@linuxfoundation.org>]

Hi, all:

Based on your feedback, I added an "auto-thankanator" mode to b4, which 
will track your use of "b4 am" and "b4 pr" and create convenient 
templated thank-you replies when you run "b4 ty".

Here's a screencast with a hands-on example:
https://asciinema.org/a/318493

I also have another example below.

Since it's an experimental feature, we just save a .thanks file instead 
of sending it outright -- at least until there's a lot more testing.  
However, if you have git-send-email set up, you can easily send that 
.thanks file off:

git send-email *.thanks

You can just hit "enter" for the questions git-send-email will try to 
ask you, as all addressee information will be taken from the message 
itself.

You can also list all tracked series and pull requests using:
b4 ty -l

They can be deleted or sent manually using "b4 ty -d" and "b4 ty -s" 
respectively (some sanity checking will be done before sending).

Please also see "b4 ty --help" for other flags.

I'd like to hear your feedback on how this feature can be improved.  
Similarly, it's possible that "b4 pr" workflow does not match how most 
people use it, so I would greatly appreciate any feedback on how that 
feature can be improved as well.

If you would like to test these features out, the repository is here:
https://git.kernel.org/pub/scm/utils/b4/b4.git/

There's probably lots of bugs in "b4 ty", but "b4 am" should be stable 
enough for daily use.

Best regards,
-K

---

Inline example:

$ b4 am -o/tmp 20200408152151.5780-1-christian.brauner@ubuntu.com
Looking up https://lore.kernel.org/r/20200408152151.5780-1-christian.brauner@ubuntu.com
Grabbing thread from lore.kernel.org
Analyzing 16 messages in the thread
---
Writing /tmp/20200408_christian_brauner_loopfs.mbx
  [✓] [PATCH 1/8] kobject_uevent: remove unneeded netlink_ns check
  [✓] [PATCH 2/8] loopfs: implement loopfs
  [✓] [PATCH 3/8] loop: use ns_capable for some loop operations
  [✓] [PATCH 4/8] kernfs: handle multiple namespace tags
  [✓] [PATCH 5/8] kernfs: let objects opt-in to propagating from the initial namespace
  [✓] [PATCH 6/8] genhd: add minimal namespace infrastructure
  [✓] [PATCH 7/8] loopfs: start attaching correct namespace during loop_add()
  [✓] [PATCH 8/8] loopfs: only show devices in their correct instance
  ---
  [✓] Attestation-by: Christian Brauner <christian.brauner@ubuntu.com> (pgp: 91C61BC06578DCA2)
---
Total patches: 8
---
Cover: /tmp/20200408_christian_brauner_loopfs.cover
 Link: https://lore.kernel.org/r/20200408152151.5780-1-christian.brauner@ubuntu.com
 Base: 7111951b8d4973bda27ff663f2cf18b663d15b48
       git checkout -b 20200408_christian_brauner_ubuntu_com 7111951b8d4973bda27ff663f2cf18b663d15b48
       git am /tmp/20200408_christian_brauner_loopfs.mbx

$ git checkout -o loopfs 7111951b8d4973bda27ff663f2cf18b663d15b48
$ git am /tmp/20200408_christian_brauner_loopfs.mbx
$ (hack-hack-hack, review-review-review)
$ git checkout master
$ git merge loopfs master --signoff

If you made no changes to the patch contents at all, you can run
"b4 ty --auto" to find that patch series in the current branch:

$ b4 ty --auto
Auto-thankanating commits in master
Found 10 of your commits since 1.week
Calculating patch hashes, may take a moment...
  Located: [PATCH 0/8] loopfs
---
Generating 1 thank-you letters
  Writing: ./christian_brauner_ubuntu_com_patch_0_8_loopfs.thanks
---
You can now run:
  git send-email ./*.thanks

The contents of christian_brauner_ubuntu_com_patch_0_8_loopfs.thanks are:

----
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: [skipped]
Cc: [skipped]
In-Reply-To: <20200408152151.5780-1-christian.brauner@ubuntu.com>
References: <20200408152151.5780-1-christian.brauner@ubuntu.com>
Subject: Re: [PATCH 0/8] loopfs
Message-Id: <158655148980.3824973.6760061710410126169.b4-ty@linuxfoundation.org>

On Wed, 8 Apr 2020 17:21:43 +0200, Christian Brauner wrote:
> Hey everyone,
> 
> After having been pinged about this by various people recently here's loopfs.
> 
> This implements loopfs, a loop device filesystem. It takes inspiration
> from the binderfs filesystem I implemented about two years ago and with
> which we had overall good experiences so far. Parts of it are also
> based on [3] but it's mostly a new, imho cleaner and more complete
> approach.
> 
> [...]

Applied, thanks!

- kobject_uevent: remove unneeded netlink_ns check
  https://git.kernel.org/mricon/c/d8f4e1e096
- loopfs: implement loopfs
  https://git.kernel.org/mricon/c/e022b26012
- loop: use ns_capable for some loop operations
  https://git.kernel.org/mricon/c/a45ab6b63c
- kernfs: handle multiple namespace tags
  https://git.kernel.org/mricon/c/9ea3d700d0
- kernfs: let objects opt-in to propagating from the initial namespace
  https://git.kernel.org/mricon/c/50b98ec6f6
- genhd: add minimal namespace infrastructure
  https://git.kernel.org/mricon/c/d01bc5a1a6
- loopfs: start attaching correct namespace during loop_add()
  https://git.kernel.org/mricon/c/be02c77ba6
- loopfs: only show devices in their correct instance
  https://git.kernel.org/mricon/c/b5cce3ce8f

Best regards,
--
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
----