On Fri, Jun 07, 2024 at 11:48:36AM +0200, Albert Esteve wrote: > > > On Fri, Jun 7, 2024 at 11:41 AM Michael S. Tsirkin <mst@xxxxxxxxxx> wrote: > > On Fri, Jun 07, 2024 at 10:00:44AM +0200, Albert Esteve wrote: > > Hi, > > > > This a formal attempt of including virtio-media > > device specification. > > This was sent to a wrong mailing list. > Please repost to the correct list. > > Albert, when you subscribed to virtio-dev you should > have received a message that read, in part: > > When to use this list: > - questions and change proposals for Virtio drivers and devices > implementing the specification. > > When not to use this list: > - questions and change proposals for the Virtio specification, > including the specification of basic functionality, transports and > devices (please use the virtio-comment mailing list > [mailto:virtio-comment@xxxxxxxxxxxxxxx] for this). > > To do: > - send email preferably in text format (best for archiving) > > Not to do: > - copy both virtio-dev and virtio-comment mailing lists (instead, pick > one) > - send full copies of the virtio spec (in any format) > > > > So what made you send a specification change proposal to > virtio-dev, and also copy the defunct, non-functional > list at virtio-dev@xxxxxxxxxxxxxxxxxxxx ? > > > Was the message unclear? If yes I'd like to improve it. > > > My bad. > The instructions were clear, and I set up the mail to be sent to the > correct virtio-dev mailing list address. Hmm no, it's actually virtio-comment@xxxxxxxxxxxxxxx for change proposals for the Virtio specification which is what you have here. > But I had the configuration > of the project set to automatically add both of the old addresses to the > patch. I only noticed after sending, so the damage was already > made. > > I will fix it for the next drop. > > > > > -- > MST > >
