b4 tool integration with virtio spec patches

[Parav Pandit <parav@nvidia.com>]

Hi All,

short summary:
virtio-dev and virtio-comment mailing lists are also now accessible at [1] and [2] to use with b4 tool [3].

OASIS lists are equally accessible as before.

[1] https://lore.kernel.org/virtio-dev/
[2] https://lore.kernel.org/virtio-comment/
[3] https://git.kernel.org/pub/scm/utils/b4/b4.git

Details:
We now have virtio-dev [1] and virtio-comment [2] mailing list accessible at lore.kernel.org for read access.

This is in addition to they are being available at existing https://lists.oasis-open.org.
Nothing changes for subscription etc at OASIS site.

Web user interface of [1] and [2] is limited compared to OASIS one.
For example, it doesn't show date/month wise emails like oasis list shows.
But the additional web interface provides different benefit.

The benefit is : it enables virtio spec devel workflow integration with tools like b4 [3].
This enables to do some automation and shared development for patches occur on dev & comment lists.

1. Anyone can now download and apply virtio spec patches with just 2 commands.
2. Acked-by, Reviewed-by etc tags automatically apply when used using b4.
3. Enables shared development

Please use it as you find it useful.
Thanks a lot, to Michael and Cornelia who dig their history emails, due to which history could be preserved at new platform.

How to use it:
(a) Install b4 tool
$ yum/apt install -y b4

(b) Find the message id of the patch series of cover-letter (or of the first patch)

(c) Download virtio spec patch series locally
$ b4 am cover.1682354275.git.mst@redhat.com 
For example, above is the message id of Michael's AQ series.

(d) Apply the patches to local git tree.
$ git am <saved_file.mbox>

Regards,
Parav Pandit