OASIS Virtual I/O Device (VIRTIO) TC

OK rusty and me addressed these comments, except two items: > Paul Knight wrote: > >   -- Add a "/" after "Committee Specification Draft 01" then a soft > return and > > then, aligned under "Committee Spec…" put "Public Review Draft 01". For > an > > example, see > > http://docs.oasis-open.org/pkcs11/pkcs11-curr/v2.40/csprd01/pkcs11-curr-v2.40-csprd01.html In this example, there's no break after "/" and neither is there in the CMIS specification. I decided we should go by these examples so no break here either - it looks prettier. > Chet Ensign wrote: > >   -- If possible, in the PDF, align the left margins. That > > is, align > "This > > version:" etc. with "Specification URIs". Not aligned now.  > > I could not figure how to fixing this one out yet. As this is cosmetic and does not affect page numbering etc, I think we can if necessary fix it after we vote, but pls note it appears like this in e.g. CMIS. -- MST Attachment: virtio-v1.0-csprd01.zip Description: Zip archive Attachment: virtio-v1.0-csd01.zip Description: Zip archive

"Michael S. Tsirkin" <mst@redhat.com> writes: > OK rusty and me addressed these comments, except two items: > >> Paul Knight wrote: >> >   -- Add a "/" after "Committee Specification Draft 01" then a soft >> return and >> > then, aligned under "Committee Spec…" put "Public Review Draft 01". For >> an >> > example, see >> > http://docs.oasis-open.org/pkcs11/pkcs11-curr/v2.40/csprd01/pkcs11-curr-v2.40-csprd01.html > > In this example, there's no break after "/" and neither is there > in the CMIS specification. I decided we should go by these examples so no > break here either - it looks prettier. I think Paul is referring to the one on the title pagem where it's: Committee Specification Public Review Draft / Public Review Draft 01 Which looks correct. >> Chet Ensign wrote: >> >   -- If possible, in the PDF, align the left margins. That >> > is, align >> "This >> > version:" etc. with "Specification URIs". Not aligned now.  >> > > > I could not figure how to fixing this one out yet. As this is > cosmetic and does not affect page numbering etc, I think we can > if necessary fix it after we vote, but pls note it appears like > this in e.g. CMIS. Hmm, I thought I fixed this, but obviously didn't. Not sure either... Thanks, Rusty.

On Tue, Dec 03, 2013 at 09:11:53PM +1030, Rusty Russell wrote: > >> Chet Ensign wrote: > >> >   -- If possible, in the PDF, align the left margins. That > >> > is, align > >> "This > >> > version:" etc. with "Specification URIs". Not aligned now.  > >> > > > > > I could not figure how to fixing this one out yet. As this is > > cosmetic and does not affect page numbering etc, I think we can > > if necessary fix it after we vote, but pls note it appears like > > this in e.g. CMIS. > > Hmm, I thought I fixed this, but obviously didn't. Not sure either... We approved 01 as is, maybe Pawel will know how to fix it for 02.

On Tue, Dec 03, 2013 at 03:58:54PM +0200, Michael S. Tsirkin wrote: > On Tue, Dec 03, 2013 at 09:11:53PM +1030, Rusty Russell wrote: > > >> Chet Ensign wrote: > > >> >   -- If possible, in the PDF, align the left margins. That > > >> > is, align > > >> "This > > >> > version:" etc. with "Specification URIs". Not aligned now.  > > >> > > > > > > > I could not figure how to fixing this one out yet. As this is > > > cosmetic and does not affect page numbering etc, I think we can > > > if necessary fix it after we vote, but pls note it appears like > > > this in e.g. CMIS. > > > > Hmm, I thought I fixed this, but obviously didn't. Not sure either... > > We approved 01 as is, maybe Pawel will know how to fix it for 02. > Heh I got it. This environment is a table so just set the column separator to 0 inch. The following will do it. Not committing until Rusty tells me it's OK. diff --git a/commands-pdf.tex b/commands-pdf.tex index 1646adb..8e278be 100644 --- a/commands-pdf.tex +++ b/commands-pdf.tex @@ -64,7 +64,7 @@
ewenvironment{oasistitlesection}[1] { -egin{tabular}{p{0in}p{5.8in}} +setlength{ abcolsep}{0in}egin{tabular}{p{0in}p{5.8in}} multicolumn{2}{l}{fontspec[Color=552681]{Arial}fontsize{10}{10} extbf{#1:}}\[-0.05in] &setlength{ opsep}{0in}setlength{parsep}{0in}setlength{partopsep}{0in} } {

"Michael S. Tsirkin" <mst@redhat.com> writes: > On Tue, Dec 03, 2013 at 03:58:54PM +0200, Michael S. Tsirkin wrote: >> On Tue, Dec 03, 2013 at 09:11:53PM +1030, Rusty Russell wrote: >> > >> Chet Ensign wrote: >> > >> >   -- If possible, in the PDF, align the left margins. That >> > >> > is, align >> > >> "This >> > >> > version:" etc. with "Specification URIs". Not aligned now.  >> > >> > >> > > >> > > I could not figure how to fixing this one out yet. As this is >> > > cosmetic and does not affect page numbering etc, I think we can >> > > if necessary fix it after we vote, but pls note it appears like >> > > this in e.g. CMIS. >> > >> > Hmm, I thought I fixed this, but obviously didn't. Not sure either... >> >> We approved 01 as is, maybe Pawel will know how to fix it for 02. >> > > > Heh I got it. This environment is a table so just set the column > separator to 0 inch. > The following will do it. > Not committing until Rusty tells me it's OK. Looks good. Please apply it for 02. Cheers, Rusty.

On Wed, Dec 04, 2013 at 02:18:33PM +1030, Rusty Russell wrote: > "Michael S. Tsirkin" <mst@redhat.com> writes: > > On Tue, Dec 03, 2013 at 03:58:54PM +0200, Michael S. Tsirkin wrote: > >> On Tue, Dec 03, 2013 at 09:11:53PM +1030, Rusty Russell wrote: > >> > >> Chet Ensign wrote: > >> > >> >   -- If possible, in the PDF, align the left margins. That > >> > >> > is, align > >> > >> "This > >> > >> > version:" etc. with "Specification URIs". Not aligned now.  > >> > >> > > >> > > > >> > > I could not figure how to fixing this one out yet. As this is > >> > > cosmetic and does not affect page numbering etc, I think we can > >> > > if necessary fix it after we vote, but pls note it appears like > >> > > this in e.g. CMIS. > >> > > >> > Hmm, I thought I fixed this, but obviously didn't. Not sure either... > >> > >> We approved 01 as is, maybe Pawel will know how to fix it for 02. > >> > > > > > > Heh I got it. This environment is a table so just set the column > > separator to 0 inch. > > The following will do it. > > Not committing until Rusty tells me it's OK. > > Looks good. Please apply it for 02. > > Cheers, > Rusty. To clarify, I was waiting for you to tag 01 so I can commit to master. I don't see it yet - did you tag? -- MST

On Wed, Dec 04, 2013 at 11:11:08AM +0200, Michael S. Tsirkin wrote: > On Wed, Dec 04, 2013 at 02:18:33PM +1030, Rusty Russell wrote: > > "Michael S. Tsirkin" <mst@redhat.com> writes: > > > On Tue, Dec 03, 2013 at 03:58:54PM +0200, Michael S. Tsirkin wrote: > > >> On Tue, Dec 03, 2013 at 09:11:53PM +1030, Rusty Russell wrote: > > >> > >> Chet Ensign wrote: > > >> > >> >   -- If possible, in the PDF, align the left margins. That > > >> > >> > is, align > > >> > >> "This > > >> > >> > version:" etc. with "Specification URIs". Not aligned now.  > > >> > >> > > > >> > > > > >> > > I could not figure how to fixing this one out yet. As this is > > >> > > cosmetic and does not affect page numbering etc, I think we can > > >> > > if necessary fix it after we vote, but pls note it appears like > > >> > > this in e.g. CMIS. > > >> > > > >> > Hmm, I thought I fixed this, but obviously didn't. Not sure either... > > >> > > >> We approved 01 as is, maybe Pawel will know how to fix it for 02. > > >> > > > > > > > > > Heh I got it. This environment is a table so just set the column > > > separator to 0 inch. > > > The following will do it. > > > Not committing until Rusty tells me it's OK. > > > > Looks good. Please apply it for 02. > > > > Cheers, > > Rusty. > > To clarify, I was waiting for you to tag 01 so I can commit to master. > I don't see it yet - did you tag? Oh. We can't tag :( I see that if we wanted to support tags we had to initially create tags and trunk under https://tools.oasis-open.org/version-control/svn/virtio/tags/ and https://tools.oasis-open.org/version-control/svn/virtio/trunk/ as opposed to putting everything directly under https://tools.oasis-open.org/version-control/svn/virtio/ . See https://tools.oasis-open.org/version-control/svn/xmile/ for an example. I guess we can still move stuff but this will affect all checked out repos so I'd like to hear from others whether we should do this. An alternative is just to record the revisions in some file and hope that OASIS will support git natively sooner rather than later. What do others think? > -- > MST

"Michael S. Tsirkin" <mst@redhat.com> writes: > On Wed, Dec 04, 2013 at 11:11:08AM +0200, Michael S. Tsirkin wrote: >> On Wed, Dec 04, 2013 at 02:18:33PM +1030, Rusty Russell wrote: >> > "Michael S. Tsirkin" <mst@redhat.com> writes: >> > > On Tue, Dec 03, 2013 at 03:58:54PM +0200, Michael S. Tsirkin wrote: >> > >> On Tue, Dec 03, 2013 at 09:11:53PM +1030, Rusty Russell wrote: >> > >> > >> Chet Ensign wrote: >> > >> > >> >   -- If possible, in the PDF, align the left margins. That >> > >> > >> > is, align >> > >> > >> "This >> > >> > >> > version:" etc. with "Specification URIs". Not aligned now.  >> > >> > >> > >> > >> > > >> > >> > > I could not figure how to fixing this one out yet. As this is >> > >> > > cosmetic and does not affect page numbering etc, I think we can >> > >> > > if necessary fix it after we vote, but pls note it appears like >> > >> > > this in e.g. CMIS. >> > >> > >> > >> > Hmm, I thought I fixed this, but obviously didn't. Not sure either... >> > >> >> > >> We approved 01 as is, maybe Pawel will know how to fix it for 02. >> > >> >> > > >> > > >> > > Heh I got it. This environment is a table so just set the column >> > > separator to 0 inch. >> > > The following will do it. >> > > Not committing until Rusty tells me it's OK. >> > >> > Looks good. Please apply it for 02. >> > >> > Cheers, >> > Rusty. >> >> To clarify, I was waiting for you to tag 01 so I can commit to master. >> I don't see it yet - did you tag? > > Oh. We can't tag :( > > I see that if we wanted to support tags we had to initially create > tags and trunk under > https://tools.oasis-open.org/version-control/svn/virtio/tags/ and > https://tools.oasis-open.org/version-control/svn/virtio/trunk/ as > opposed to putting everything directly under > https://tools.oasis-open.org/version-control/svn/virtio/ . > See > https://tools.oasis-open.org/version-control/svn/xmile/ > for an example. > > I guess we can still move stuff but this will affect all checked > out repos so I'd like to hear from others whether we should do this. > An alternative is just to record the revisions in some file > and hope that OASIS will support git natively sooner rather than > later. > > What do others think? Don't mess with the repo. My thoughts: 1) Remove the txt version, since it's out of date anyway. 2) Add a REVISION file with "02" in it. 3) Make the scripts use REVISION. Cheers, Rusty.