All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Stabellini <sstabellini@kernel.org>
To: Al Stone <al.stone@linaro.org>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
	wei.liu2@citrix.com, graeme.gregory@linaro.org,
	konrad.wilk@oracle.com, George.Dunlap@eu.citrix.com,
	andrew.cooper3@citrix.com,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	tim@xen.org, julien.grall@arm.com, jbeulich@suse.com,
	xen-devel@lists.xenproject.org, parth.dixit@linaro.org,
	roger.pau@citrix.com
Subject: Re: STAO spec in xen.git
Date: Fri, 13 Jan 2017 13:00:34 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.2.10.1701131257200.18352@sstabellini-ThinkPad-X260> (raw)
In-Reply-To: <7b7a9c05-d45f-306d-ff69-3d442a73e127@linaro.org>

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

  reply	other threads:[~2017-01-13 21:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-13 19:03 STAO spec in xen.git Stefano Stabellini
2017-01-13 19:34 ` Ian Jackson
2017-01-13 19:47   ` Julien Grall
2017-01-13 19:56     ` Stefano Stabellini
2017-01-17 15:29     ` Olaf Hering
2017-01-17 19:57       ` Stefano Stabellini
2017-02-14 16:27         ` Olaf Hering
2017-02-14 18:25           ` Stefano Stabellini
2017-02-14 18:39             ` Olaf Hering
2017-02-14 20:02             ` Olaf Hering
2017-02-14 20:27               ` Wei Liu
2017-02-15  9:11                 ` Olaf Hering
2017-02-15 19:42                   ` Stefano Stabellini
2017-01-13 19:52   ` Stefano Stabellini
2017-01-13 20:37     ` Al Stone
2017-01-13 21:00       ` Stefano Stabellini [this message]
2017-01-16 11:26         ` Ian Jackson
2017-01-16 15:34           ` Roger Pau Monné
2017-01-16 18:40           ` Stefano Stabellini
2017-01-17  4:55             ` Juergen Gross
2017-01-17 15:18               ` Andrew Cooper

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.10.1701131257200.18352@sstabellini-ThinkPad-X260 \
    --to=sstabellini@kernel.org \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=al.stone@linaro.org \
    --cc=andrew.cooper3@citrix.com \
    --cc=graeme.gregory@linaro.org \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=julien.grall@arm.com \
    --cc=konrad.wilk@oracle.com \
    --cc=parth.dixit@linaro.org \
    --cc=roger.pau@citrix.com \
    --cc=tim@xen.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.