STAO spec in xen.git

STAO spec in xen.git

[Stefano Stabellini]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 404 bytes --]

Hi all,

I suggest we commit the STAO spec in the form of the attached ODT
document to xen.git under docs/misc, for easier editing and consumption
by the Xen community, and to be able to generate a stable URL for it. In
fact at the moment the link to the STAO spec from http://uefi.org/acpi
is broken. Once we have a stable URL, we'll fix the link.

Let me know if you are OK with this.

Cheers,

Stefano

[-- Attachment #2: Type: APPLICATION/vnd.oasis.opendocument.text, Size: 20206 bytes --]

[-- Attachment #3: Type: text/plain, Size: 127 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: STAO spec in xen.git

[Ian Jackson]

Stefano Stabellini writes ("STAO spec in xen.git"):
> I suggest we commit the STAO spec in the form of the attached ODT
> document to xen.git under docs/misc, for easier editing and consumption
> by the Xen community, and to be able to generate a stable URL for it. In
> fact at the moment the link to the STAO spec from http://uefi.org/acpi
> is broken. Once we have a stable URL, we'll fix the link.
> 
> Let me know if you are OK with this.

I think this is a fine place to keep them.

Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
(for both this and the XENV one)

What stable URL do you propose to use ?

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: STAO spec in xen.git

[Julien Grall]

[-- Attachment #1.1: Type: text/plain, Size: 2042 bytes --]

Hi,

Sorry for the top postimg and formatting. I am sending this e-mail from my phone.

We already had this discussion a couple of months ago (see [1]). We agreed on an URL but the pdfs were not uploaded.

Regarding the format. Does ODT will allow git to do proper diff?
If not I would prefer the markdown format to be used.

Cheers,

[1] https://lists.xen.org/archives/html/xen-devel/2016-11/msg00577.html
________________________________
From: Xen-devel <xen-devel-bounces@lists.xen.org> on behalf of Ian Jackson <ian.jackson@eu.citrix.com>
Sent: Friday, January 13, 2017 7:34:57 PM
To: Stefano Stabellini
Cc: wei.liu2@citrix.com; al.stone@linaro.org; graeme.gregory@linaro.org; konrad.wilk@oracle.com; George.Dunlap@eu.citrix.com; andrew.cooper3@citrix.com; tim@xen.org; Julien Grall; jbeulich@suse.com; xen-devel@lists.xenproject.org; parth.dixit@linaro.org; roger.pau@citrix.com
Subject: Re: [Xen-devel] STAO spec in xen.git

Stefano Stabellini writes ("STAO spec in xen.git"):
> I suggest we commit the STAO spec in the form of the attached ODT
> document to xen.git under docs/misc, for easier editing and consumption
> by the Xen community, and to be able to generate a stable URL for it. In
> fact at the moment the link to the STAO spec from http://uefi.org/acpi
> is broken. Once we have a stable URL, we'll fix the link.
>
> Let me know if you are OK with this.

I think this is a fine place to keep them.

Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
(for both this and the XENV one)

What stable URL do you propose to use ?

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

[-- Attachment #1.2: Type: text/html, Size: 2956 bytes --]

[-- Attachment #2: Type: text/plain, Size: 127 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: STAO spec in xen.git

[Stefano Stabellini]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 2452 bytes --]

Hi Julien,

I tried markdown, but there are too many tables, they all get garbled.
git diff would only show binary diffs, but libreoffice can show changes.

Cheers,

Stefano

On Fri, 13 Jan 2017, Julien Grall wrote:
> Hi,
> 
> Sorry for the top postimg and formatting. I am sending this e-mail from my phone.
> 
> We already had this discussion a couple of months ago (see [1]). We agreed on an URL but the pdfs were not uploaded.
> 
> Regarding the format. Does ODT will allow git to do proper diff?
> If not I would prefer the markdown format to be used.
> 
> Cheers,
> 
> [1] https://lists.xen.org/archives/html/xen-devel/2016-11/msg00577.html
> 
> _______________________________________________________________________________________________________________________________________________________________________________
> From: Xen-devel <xen-devel-bounces@lists.xen.org> on behalf of Ian Jackson <ian.jackson@eu.citrix.com>
> Sent: Friday, January 13, 2017 7:34:57 PM
> To: Stefano Stabellini
> Cc: wei.liu2@citrix.com; al.stone@linaro.org; graeme.gregory@linaro.org; konrad.wilk@oracle.com; George.Dunlap@eu.citrix.com; andrew.cooper3@citrix.com; tim@xen.org; Julien
> Grall; jbeulich@suse.com; xen-devel@lists.xenproject.org; parth.dixit@linaro.org; roger.pau@citrix.com
> Subject: Re: [Xen-devel] STAO spec in xen.git  
> Stefano Stabellini writes ("STAO spec in xen.git"):
> > I suggest we commit the STAO spec in the form of the attached ODT
> > document to xen.git under docs/misc, for easier editing and consumption
> > by the Xen community, and to be able to generate a stable URL for it. In
> > fact at the moment the link to the STAO spec from http://uefi.org/acpi
> > is broken. Once we have a stable URL, we'll fix the link.
> >
> > Let me know if you are OK with this.
> 
> I think this is a fine place to keep them.
> 
> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
> (for both this and the XENV one)
> 
> What stable URL do you propose to use ?
> 
> Ian.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel
> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender
> immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
> 

[-- Attachment #2: Type: text/plain, Size: 127 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: STAO spec in xen.git

[Olaf Hering]

[-- Attachment #1.1: Type: text/plain, Size: 195 bytes --]

On Fri, Jan 13, Julien Grall wrote:

> Regarding the format. Does ODT will allow git to do proper diff?

There is flat ODT, "Safe as ..." and pick the better format from the pulldown menu.

Olaf

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 127 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: STAO spec in xen.git

[Stefano Stabellini]

On Tue, 17 Jan 2017, Olaf Hering wrote:
> On Fri, Jan 13, Julien Grall wrote:
> 
> > Regarding the format. Does ODT will allow git to do proper diff?
> 
> There is flat ODT, "Safe as ..." and pick the better format from the pulldown menu.

Sounds like a good idea. Can you submit a patch?

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: STAO spec in xen.git

[Olaf Hering]

[-- Attachment #1.1: Type: text/plain, Size: 538 bytes --]

On Tue, Jan 17, Stefano Stabellini wrote:

> On Tue, 17 Jan 2017, Olaf Hering wrote:
> > On Fri, Jan 13, Julien Grall wrote:
> > 
> > > Regarding the format. Does ODT will allow git to do proper diff?
> > 
> > There is flat ODT, "Safe as ..." and pick the better format from the pulldown menu.
> 
> Sounds like a good idea. Can you submit a patch?

Done, see 'docs: convert from binary to ASCII'.

For some reason results of 'git rm' are not noticed by
get-maintainer.pl, see xen-devel for a copy of the removal.


Olaf

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 127 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: STAO spec in xen.git

[Stefano Stabellini]

On Tue, 14 Feb 2017, Olaf Hering wrote:
> On Tue, Jan 17, Stefano Stabellini wrote:
> 
> > On Tue, 17 Jan 2017, Olaf Hering wrote:
> > > On Fri, Jan 13, Julien Grall wrote:
> > > 
> > > > Regarding the format. Does ODT will allow git to do proper diff?
> > > 
> > > There is flat ODT, "Safe as ..." and pick the better format from the pulldown menu.
> > 
> > Sounds like a good idea. Can you submit a patch?
> 
> Done, see 'docs: convert from binary to ASCII'.
> 
> For some reason results of 'git rm' are not noticed by
> get-maintainer.pl, see xen-devel for a copy of the removal.

Interestingly, my "git am" is unable to apply those patches. Does it
work for you? I cannot see anything wrong with them, but they don't
work. If the problem is that they are too large, please send the files
as attachments.

Also, I tried to do the same conversion with my copy of Libreoffice and
the FODT files produced are significantly different from yours, which
means, even if we use FODT docs, we are probably going to be unable to
send changes as meaningful text patches.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: STAO spec in xen.git

[Olaf Hering]

[-- Attachment #1.1: Type: text/plain, Size: 475 bytes --]

On Tue, Feb 14, Stefano Stabellini wrote:

> Also, I tried to do the same conversion with my copy of Libreoffice and
> the FODT files produced are significantly different from yours, which
> means, even if we use FODT docs, we are probably going to be unable to
> send changes as meaningful text patches.

I guess one would be able to use vi to make further adjustments.

So far I have not tried to apply what git send-email produced, it would
be a dead-end anyway :-)

Olaf

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 127 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: STAO spec in xen.git

[Olaf Hering]

[-- Attachment #1.1: Type: text/plain, Size: 499 bytes --]

On Tue, Feb 14, Stefano Stabellini wrote:

> Interestingly, my "git am" is unable to apply those patches. Does it
> work for you? I cannot see anything wrong with them, but they don't
> work. If the problem is that they are too large, please send the files
> as attachments.

Its the '\ No newline at end of file' at the end. Not sure if diff
should not procude it, or if patch should handle it. I assume an
attachment would create the same error because there is no newline for
some reason.


Olaf

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 127 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: STAO spec in xen.git

[Wei Liu]

On Tue, Feb 14, 2017 at 09:02:14PM +0100, Olaf Hering wrote:
> On Tue, Feb 14, Stefano Stabellini wrote:
> 
> > Interestingly, my "git am" is unable to apply those patches. Does it
> > work for you? I cannot see anything wrong with them, but they don't
> > work. If the problem is that they are too large, please send the files
> > as attachments.
> 
> Its the '\ No newline at end of file' at the end. Not sure if diff
> should not procude it, or if patch should handle it. I assume an
> attachment would create the same error because there is no newline for
> some reason.
> 

Better to just push to a branch for us to fetch.

Wei.

> 
> Olaf



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: STAO spec in xen.git

[Olaf Hering]

[-- Attachment #1.1: Type: text/plain, Size: 271 bytes --]

Am Tue, 14 Feb 2017 20:27:15 +0000
schrieb Wei Liu <wei.liu2@citrix.com>:

> Better to just push to a branch for us to fetch.

That would be git://github.com/olafhering/xen.git#libreoffice

https://github.com/olafhering/xen/commits/libreoffice

Thanks,

Olaf

[-- Attachment #1.2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 127 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: STAO spec in xen.git

[Stefano Stabellini]

On Wed, 15 Feb 2017, Olaf Hering wrote:
> Am Tue, 14 Feb 2017 20:27:15 +0000
> schrieb Wei Liu <wei.liu2@citrix.com>:
> 
> > Better to just push to a branch for us to fetch.
> 
> That would be git://github.com/olafhering/xen.git#libreoffice
> 
> https://github.com/olafhering/xen/commits/libreoffice
> 

Thanks, pulled

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: STAO spec in xen.git

[Stefano Stabellini]

On Fri, 13 Jan 2017, Ian Jackson wrote:
> Stefano Stabellini writes ("STAO spec in xen.git"):
> > I suggest we commit the STAO spec in the form of the attached ODT
> > document to xen.git under docs/misc, for easier editing and consumption
> > by the Xen community, and to be able to generate a stable URL for it. In
> > fact at the moment the link to the STAO spec from http://uefi.org/acpi
> > is broken. Once we have a stable URL, we'll fix the link.
> > 
> > Let me know if you are OK with this.
> 
> I think this is a fine place to keep them.
> 
> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
> (for both this and the XENV one)
> 
> What stable URL do you propose to use ?

I don't have a preference, as long as it is truly stable :-)

This is a question for people more familiar with ASWG than me. Is it OK
to publish it in ODT? I have just noticed that this would be the first
spec in that format among the ones linked from http://uefi.org/acpi.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: STAO spec in xen.git

[Al Stone]

On 01/13/2017 12:52 PM, Stefano Stabellini wrote:
> On Fri, 13 Jan 2017, Ian Jackson wrote:
>> Stefano Stabellini writes ("STAO spec in xen.git"):
>>> I suggest we commit the STAO spec in the form of the attached ODT
>>> document to xen.git under docs/misc, for easier editing and consumption
>>> by the Xen community, and to be able to generate a stable URL for it. In
>>> fact at the moment the link to the STAO spec from http://uefi.org/acpi
>>> is broken. Once we have a stable URL, we'll fix the link.
>>>
>>> Let me know if you are OK with this.
>>
>> I think this is a fine place to keep them.
>>
>> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
>> (for both this and the XENV one)
>>
>> What stable URL do you propose to use ?
> 
> I don't have a preference, as long as it is truly stable :-)
> 
> This is a question for people more familiar with ASWG than me. Is it OK
> to publish it in ODT? I have just noticed that this would be the first
> spec in that format among the ones linked from http://uefi.org/acpi.
> 

I would recommend exporting it as PDF and submitting those to UEFI.  For
good or bad, the convention has been to use Word format within the ASWG,
and PDF to publish public documents (though there are exceptions...).

Let me know off line if you need assistance making sure the uefi.org links
get updated properly.

-- 
ciao,
al
-----------------------------------
Al Stone
Software Engineer
Linaro Enterprise Group
al.stone@linaro.org
-----------------------------------

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: STAO spec in xen.git

[Stefano Stabellini]

On Fri, 13 Jan 2017, Al Stone wrote:
> On 01/13/2017 12:52 PM, Stefano Stabellini wrote:
> > On Fri, 13 Jan 2017, Ian Jackson wrote:
> >> Stefano Stabellini writes ("STAO spec in xen.git"):
> >>> I suggest we commit the STAO spec in the form of the attached ODT
> >>> document to xen.git under docs/misc, for easier editing and consumption
> >>> by the Xen community, and to be able to generate a stable URL for it. In
> >>> fact at the moment the link to the STAO spec from http://uefi.org/acpi
> >>> is broken. Once we have a stable URL, we'll fix the link.
> >>>
> >>> Let me know if you are OK with this.
> >>
> >> I think this is a fine place to keep them.
> >>
> >> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
> >> (for both this and the XENV one)
> >>
> >> What stable URL do you propose to use ?
> > 
> > I don't have a preference, as long as it is truly stable :-)
> > 
> > This is a question for people more familiar with ASWG than me. Is it OK
> > to publish it in ODT? I have just noticed that this would be the first
> > spec in that format among the ones linked from http://uefi.org/acpi.
> > 
> 
> I would recommend exporting it as PDF and submitting those to UEFI.  For
> good or bad, the convention has been to use Word format within the ASWG,
> and PDF to publish public documents (though there are exceptions...).

In that case, I think we should still commit it as ODT, but convert it
automatically to PDF when we publish it (we do something similar with
the markdown docs, converting them from markdown to html).


> Let me know off line if you need assistance making sure the uefi.org links
> get updated properly.

We'll most certainly need your help, thanks.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: STAO spec in xen.git

[Ian Jackson]

Stefano Stabellini writes ("Re: STAO spec in xen.git"):
> In that case, I think we should still commit it as ODT, but convert it
> automatically to PDF when we publish it (we do something similar with
> the markdown docs, converting them from markdown to html).

Exactly.

The fact that git diff won't show updates well is not ideal, but IMO
it is imperative to get the document 1. it into our own version
control and 2. in a format we can edit 3. using FLOSS tools.

Please can we commit the source of the document to xen.git as a first
step.  At that point the xen.git copy will become the master copy.

We can then think about PDF export.  If the conversion has to be done
ad hoc manually at first then that is not a blocker for committing the
file.

Thanks,
Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: STAO spec in xen.git

[Roger Pau Monné]

On Mon, Jan 16, 2017 at 11:26:57AM +0000, Ian Jackson wrote:
> Stefano Stabellini writes ("Re: STAO spec in xen.git"):
> > In that case, I think we should still commit it as ODT, but convert it
> > automatically to PDF when we publish it (we do something similar with
> > the markdown docs, converting them from markdown to html).
> 
> Exactly.
> 
> The fact that git diff won't show updates well is not ideal, but IMO
> it is imperative to get the document 1. it into our own version
> control and 2. in a format we can edit 3. using FLOSS tools.
> 
> Please can we commit the source of the document to xen.git as a first
> step.  At that point the xen.git copy will become the master copy.
> 
> We can then think about PDF export.  If the conversion has to be done
> ad hoc manually at first then that is not a blocker for committing the
> file.

unoconv[0][1] seems like a good option to do cli conversions from odt to pdf.
Adding a configure test plus a matching make rune doesn't seem very hard.

Roger.

[0] https://github.com/dagwieers/unoconv
[1] https://packages.debian.org/search?keywords=unoconv

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: STAO spec in xen.git

[Stefano Stabellini]

On Mon, 16 Jan 2017, Ian Jackson wrote:
> Stefano Stabellini writes ("Re: STAO spec in xen.git"):
> > In that case, I think we should still commit it as ODT, but convert it
> > automatically to PDF when we publish it (we do something similar with
> > the markdown docs, converting them from markdown to html).
> 
> Exactly.
> 
> The fact that git diff won't show updates well is not ideal, but IMO
> it is imperative to get the document 1. it into our own version
> control and 2. in a format we can edit 3. using FLOSS tools.
> 
> Please can we commit the source of the document to xen.git as a first
> step.  At that point the xen.git copy will become the master copy.
> 
> We can then think about PDF export.  If the conversion has to be done
> ad hoc manually at first then that is not a blocker for committing the
> file.

Right. I am going to commit this version for now.

If somebody was willing to come up with an alternative version of this
document in a more git-friendly format, I would be more than happy for
it to replace the ODT version.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: STAO spec in xen.git

[Juergen Gross]

On 16/01/17 19:40, Stefano Stabellini wrote:
> On Mon, 16 Jan 2017, Ian Jackson wrote:
>> Stefano Stabellini writes ("Re: STAO spec in xen.git"):
>>> In that case, I think we should still commit it as ODT, but convert it
>>> automatically to PDF when we publish it (we do something similar with
>>> the markdown docs, converting them from markdown to html).
>>
>> Exactly.
>>
>> The fact that git diff won't show updates well is not ideal, but IMO
>> it is imperative to get the document 1. it into our own version
>> control and 2. in a format we can edit 3. using FLOSS tools.
>>
>> Please can we commit the source of the document to xen.git as a first
>> step.  At that point the xen.git copy will become the master copy.
>>
>> We can then think about PDF export.  If the conversion has to be done
>> ad hoc manually at first then that is not a blocker for committing the
>> file.
> 
> Right. I am going to commit this version for now.
> 
> If somebody was willing to come up with an alternative version of this
> document in a more git-friendly format, I would be more than happy for
> it to replace the ODT version.

LaTeX? Should be less than 1 hour work. I can do it if a .tex file is
okay.


Juergen


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: STAO spec in xen.git

[Andrew Cooper]

On 17/01/17 04:55, Juergen Gross wrote:
> On 16/01/17 19:40, Stefano Stabellini wrote:
>> On Mon, 16 Jan 2017, Ian Jackson wrote:
>>> Stefano Stabellini writes ("Re: STAO spec in xen.git"):
>>>> In that case, I think we should still commit it as ODT, but convert it
>>>> automatically to PDF when we publish it (we do something similar with
>>>> the markdown docs, converting them from markdown to html).
>>> Exactly.
>>>
>>> The fact that git diff won't show updates well is not ideal, but IMO
>>> it is imperative to get the document 1. it into our own version
>>> control and 2. in a format we can edit 3. using FLOSS tools.
>>>
>>> Please can we commit the source of the document to xen.git as a first
>>> step.  At that point the xen.git copy will become the master copy.
>>>
>>> We can then think about PDF export.  If the conversion has to be done
>>> ad hoc manually at first then that is not a blocker for committing the
>>> file.
>> Right. I am going to commit this version for now.
>>
>> If somebody was willing to come up with an alternative version of this
>> document in a more git-friendly format, I would be more than happy for
>> it to replace the ODT version.
> LaTeX? Should be less than 1 hour work. I can do it if a .tex file is
> okay.

We have had LaTeX documents in the past in tree.  It certainly would be
more text-friendly.

~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel