Re: [PATCH v2 0/1] virtio-media: Add device specification
Albert Esteve <[email protected]> Fri, 7 Jun 2024 11:48:36 +0200
| Newsgroups | dev.linux.lists.virtio-dev |
|---|---|
| Message-ID | <CADSE00KP+dsN5W0DHzML8f4wjiH-NQEifQ5zxLusw65mEUb+wA@mail.gmail.com> |
On Fri, Jun 7, 2024 at 11:41 AM Michael S. Tsirkin <[email protected]> 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:[email protected]] 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 [email protected] ? > > > 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. 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 > >