From: Stefano Stabellini <sstabellini@kernel.org>
To: Olaf Hering <olaf@aepfle.de>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
"wei.liu2@citrix.com" <wei.liu2@citrix.com>,
"al.stone@linaro.org" <al.stone@linaro.org>,
"graeme.gregory@linaro.org" <graeme.gregory@linaro.org>,
"George.Dunlap@eu.citrix.com" <George.Dunlap@eu.citrix.com>,
"andrew.cooper3@citrix.com" <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
"tim@xen.org" <tim@xen.org>, Julien Grall <Julien.Grall@arm.com>,
"jbeulich@suse.com" <jbeulich@suse.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"parth.dixit@linaro.org" <parth.dixit@linaro.org>,
"roger.pau@citrix.com" <roger.pau@citrix.com>
Subject: Re: STAO spec in xen.git
Date: Tue, 14 Feb 2017 10:25:49 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.10.1702141021230.6418@sstabellini-ThinkPad-X260> (raw)
In-Reply-To: <20170214162723.GE28313@aepfle.de>
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
next prev parent reply other threads:[~2017-02-14 18:25 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 [this message]
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
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.1702141021230.6418@sstabellini-ThinkPad-X260 \
--to=sstabellini@kernel.org \
--cc=George.Dunlap@eu.citrix.com \
--cc=Julien.Grall@arm.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=olaf@aepfle.de \
--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.