RE: [PATCH v1 00/20] Split device spec to its individual files

[Parav Pandit <parav@nvidia.com>]

> From: Michael S. Tsirkin <mst@redhat.com>
> Sent: Tuesday, January 3, 2023 11:19 AM
> 
> On Tue, Jan 03, 2023 at 04:04:11PM +0000, Parav Pandit wrote:
> >
> > > From: Michael S. Tsirkin <mst@redhat.com>
> > > Sent: Tuesday, January 3, 2023 10:44 AM
> >
> >
> > > > I was writing up reply to other thread at the moment.
> > > > But lets continue here since you ask.
> > > > I don't have a strong opinion, but I find directories neat.
> > > > This is because we have many devices spec files, conformance files
> > > > and it's
> > > expected to grow.
> > > > I have transports directory and place code in there.
> > > > Since latex spec doesn't have good way to include and refer sub
> > > > section, we
> > > have many files.
> > > > 19 devices * 3 spec files + 3 transports * 3 spec files.
> > > >
> > > > And once spec is in its own directory, things should be self-sufficient.
> > > > Only touch points will be in common areas which should be less frequent.
> > > > WDYT?
> > >
> > > Yea I know. It's just that one of the ways we publish is a directory
> > > in a web browser
> > Do you mean browsing https://github.com/oasis-tcs/virtio-spec/ in a web
> browser?
> 
> No, the one at oasis:
> 
> https://docs.oasis-open.org/virtio/virtio/v1.1/cs01/tex/
> 
> this is technically the authoritative one.
> 
Ok. I get it.
Shall we continue with currently proposed directory?

> 
> > > and there browsing up and down is annoying.
> > > But if you feel strongly we can make the TC decide.
> > At least I am less browsing from the web browser.
> > The two common cases I came across are,
> > (a) either users read via pdf/html views or
> > (b) developers editing them and find useful to see related things in one
> directory.
> >
> > Lets start with directories and if TC has better suggestion, we can change.