Re: b4 submit ready for beta testing

[Konstantin Ryabitsev <konstantin@linuxfoundation.org>]

Hello, all:

Based on your feedback, I've refactored the submit functionality and it's
ready for some more poking and testing. Here are the implemented changes:

1. Pluggable cover letter strategies
   The goal is to support 3 different cover-letter strategies:

   "commit": same as first implementation with the cover letter stored in an
   empty commit at the beginning of the series.

   "branch-description": stores the cover letter in the branch description
   (which really just means the git config file). The cover letter can be
   edited using the same b4 --cover-letter command, or just with "git branch
   --edit-description".

   "tag" (not yet implemented): will store the cover letter in tags a-la
   git-publish.

   The default cover strategy remains "commit", but you can switch using
   b4.ez-cover-strategy, e.g. in your ~/.gitconfig:

       [b4]
         ez-cover-strategy = branch-description

  Note, that switching from one to the other for existing tracked series is
  not supported (and I'm not sure will be). It's also not currently possible
  to enroll an existing branch into ez-series with the "commit" strategy
  (because I haven't yet figured out how to insert a random commit into
  history with git-filter-repo, but I'm sure it's possible).

2. "b4 submit" command got split into 3 different commands:

  - "b4 ez-series" to create/enroll branches and manage cover letters

  - "b4 ez-trailers" for retrieving trailer updates and updating your local
    branch. Note, that with -F this can run on any branch, not necessarily the
    branch managed by ez-series. E.g.:

        git checkout arbitrary-branch
        b4 ez-trailers -us -F [arbitrary-msgid]

  - "b4 ez-send" for sending the series to the mailing list. It has all the
    same flags as formerly for "b4 submit", e.g.:

        b4 ez-send --no-auto-to-cc --dry-run

    There is no more --reroll command, as using ez-send will automatically
    increment the tracked revision number (unless RESEND was in the prefixes).

    There's still no support on the web submission endpoint, but it's coming
    in the near future.

Thank you for everyone's feedback, and please continue testing it out. If you
want to test the dev version of b4, use the same instructions:

> ## Getting the b4 dev version
> 
> To install the b4 development version, you will need to run it from the git
> checkout:
> 
>   git clone https://git.kernel.org/pub/scm/utils/b4/b4.git
>   cd b4
>   git submodule update --init
>   alias b4="$PWD/b4.sh"
> 
> You can find out more details in the README file. You will also want to make
> sure that git-filter-repo is installed (either from your distro packages or
> from pip).
> 
> If you're already running b4 from the git checkout, make sure you run "git
> submodule update" to pull in the latest unreleased patatt version.

Best regards,
Konstantin