From: Cornelia Huck <cohuck@redhat.com>
To: Parav Pandit <parav@nvidia.com>, "Michael S. Tsirkin" <mst@redhat.com>
Cc: "virtio-comment@lists.linux.dev" <virtio-comment@lists.linux.dev>
Subject: RE: [PATCH v3] README.md: update mailing list info
Date: Tue, 21 May 2024 11:58:40 +0200 [thread overview]
Message-ID: <874jar8p0v.fsf@redhat.com> (raw)
In-Reply-To: <PH0PR12MB5481168F6B161E51F8251992DCEA2@PH0PR12MB5481.namprd12.prod.outlook.com>
On Tue, May 21 2024, Parav Pandit <parav@nvidia.com> wrote:
>> From: Michael S. Tsirkin <mst@redhat.com>
>> Sent: Tuesday, May 21, 2024 12:55 PM
>>
>> On Tue, May 21, 2024 at 04:19:31AM +0000, Parav Pandit wrote:
>> > Hi Michael,
>> >
>> > > From: Michael S. Tsirkin <mst@redhat.com>
>> > > Sent: Wednesday, May 15, 2024 4:07 PM
>> >
>> > > > > I would wait until next Monday at least. Give everyone time to
>> > > > > subscribe to the new list.
>> >
>> > Can you please merge this patch?
>>
>> Pushed now.
>
> Thanks Michael.
> Cornelia mentioned in [1] that master and 1.4 should be merged.
> 1.4 is 17 patches behind the master including this one.
> And 12 commits behind..
>
> Can you please merge them? Without it, there are conflicts in patches.
>
> Also, we need to update in the README.md on which branch to use for sending the patches.
>
> [1] https://lists.oasis-open.org/archives/virtio-comment/202401/msg00087.html
Repo status is a mess, because the state of the TC is currently a
mess...
* Before we can merge the branches, we need to do a proper Special
Majority Vote to release 1.3 (which had been delayed since *last year*
due to first the threatening migration, and then the actual
troublesome migration.)
* The platform is still not working properly. For starters, we now know
that other people besides myself are not getting any mail from the
main TC list; given that the ballot approving use of the new lists has
not gotten a vote from several usually reliable voters, I fear that
mail delivery regarding ballots is broken for some people as well...
Before requesting a Special Majority Vote, IMNSHO we need to be sure
that voters actually get notified about it. [We have raised the issues
with mail delivery with OASIS staff, but I'm really unsure about the
current status.]
virtio-comment subscribers who are TC members as well: if you didn't get
any emails from either the main TC mailing list (you can check the
archives) or from the voting platform, we'd like to hear about it.
next prev parent reply other threads:[~2024-05-21 9:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 9:53 [PATCH v3] README.md: update mailing list info Michael S. Tsirkin
2024-05-15 10:14 ` Parav Pandit
2024-05-15 10:30 ` Michael S. Tsirkin
2024-05-15 10:32 ` Parav Pandit
2024-05-15 10:37 ` Michael S. Tsirkin
2024-05-21 4:19 ` Parav Pandit
2024-05-21 7:24 ` Michael S. Tsirkin
2024-05-21 7:59 ` Parav Pandit
2024-05-21 8:03 ` Michael S. Tsirkin
2024-05-21 8:06 ` Parav Pandit
2024-05-21 9:58 ` Cornelia Huck [this message]
2024-05-21 12:02 ` Parav Pandit
2024-05-21 12:07 ` Michael S. Tsirkin
2024-05-21 12:42 ` Cornelia Huck
2024-05-21 13:24 ` Parav Pandit
2024-05-21 14:32 ` Michael S. Tsirkin
2024-05-16 8:15 ` Stefano Garzarella
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=874jar8p0v.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=parav@nvidia.com \
--cc=virtio-comment@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.