All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Stabellini <sstabellini@kernel.org>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
	wei.liu2@citrix.com, Al Stone <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@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: Mon, 16 Jan 2017 10:40:12 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.2.10.1701161038190.2960@sstabellini-ThinkPad-X260> (raw)
In-Reply-To: <22652.44545.606227.691347@mariner.uk.xensource.com>

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

  parent reply	other threads:[~2017-01-16 18:40 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
2017-01-16 11:26         ` Ian Jackson
2017-01-16 15:34           ` Roger Pau Monné
2017-01-16 18:40           ` Stefano Stabellini [this message]
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.1701161038190.2960@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.