From: Kevin Buckley <kevin.buckley.ecs.vuw.ac.nz@gmail.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel@lists.xenproject.org,
Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: Xen commit 9b0bc91b3 possibly removed too much info from README
Date: Tue, 16 Apr 2019 21:31:41 +0800 [thread overview]
Message-ID: <CABwOO=cyX0PcuvbfYu1ZyN384604sT2HPAoJR+cknFqWH-e7PQ@mail.gmail.com> (raw)
In-Reply-To: <20190415093632.GN30543@zion.uk.xensource.com>
> Oh wait, I don't think there is anything to fix there. Those sentences
> look repetitive but they do say different things: in tools case, it says
> "repos will be cloned"; in stubdom case, it says "external packages
> will be downloaded. So they do reflect correctly what will happen.
>
Let me narrow things down a bit further to highlight the duplication
----8<--------8<--------8<--------8<--------8<--------8<--------8<--------8<----
During tools build external repos will be cloned into the source tree. <=== 1
This variable can be used to point to a different git binary to be used.
GIT=
During tools build external repos will be cloned into the source tree. <=== 2
During stubdom build external packages will be downloaded into the
source tree. These variables can be used to point to a different
locations.
XEN_EXTFILES_URL=
OVMF_UPSTREAM_URL=
----8<--------8<--------8<--------8<--------8<--------8<--------8<--------8<----
Hope that's clearer ?
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Buckley <kevin.buckley.ecs.vuw.ac.nz@gmail.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel@lists.xenproject.org,
Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: [Xen-devel] Xen commit 9b0bc91b3 possibly removed too much info from README
Date: Tue, 16 Apr 2019 21:31:41 +0800 [thread overview]
Message-ID: <CABwOO=cyX0PcuvbfYu1ZyN384604sT2HPAoJR+cknFqWH-e7PQ@mail.gmail.com> (raw)
Message-ID: <20190416133141.O5tvrRmpc39A-FSFIOdhTpfbeX_N3vz_QBzdcVt8xZ4@z> (raw)
In-Reply-To: <20190415093632.GN30543@zion.uk.xensource.com>
> Oh wait, I don't think there is anything to fix there. Those sentences
> look repetitive but they do say different things: in tools case, it says
> "repos will be cloned"; in stubdom case, it says "external packages
> will be downloaded. So they do reflect correctly what will happen.
>
Let me narrow things down a bit further to highlight the duplication
----8<--------8<--------8<--------8<--------8<--------8<--------8<--------8<----
During tools build external repos will be cloned into the source tree. <=== 1
This variable can be used to point to a different git binary to be used.
GIT=
During tools build external repos will be cloned into the source tree. <=== 2
During stubdom build external packages will be downloaded into the
source tree. These variables can be used to point to a different
locations.
XEN_EXTFILES_URL=
OVMF_UPSTREAM_URL=
----8<--------8<--------8<--------8<--------8<--------8<--------8<--------8<----
Hope that's clearer ?
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-04-16 13:31 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 8:09 Xen commit 9b0bc91b3 possibly removed too much info from README Kevin Buckley
2019-04-11 8:09 ` [Xen-devel] " Kevin Buckley
2019-04-11 10:28 ` Wei Liu
2019-04-11 10:28 ` [Xen-devel] " Wei Liu
2019-04-13 3:17 ` Kevin Buckley
2019-04-13 3:17 ` [Xen-devel] " Kevin Buckley
2019-04-15 9:23 ` Wei Liu
2019-04-15 9:23 ` [Xen-devel] " Wei Liu
2019-04-15 9:36 ` Wei Liu
2019-04-15 9:36 ` [Xen-devel] " Wei Liu
2019-04-16 13:31 ` Kevin Buckley [this message]
2019-04-16 13:31 ` Kevin Buckley
2019-05-13 13:40 ` Wei Liu
2019-05-13 13:40 ` [Xen-devel] " Wei Liu
2019-04-16 13:28 ` Kevin Buckley
2019-04-16 13:28 ` [Xen-devel] " Kevin Buckley
2019-04-17 9:56 ` Wei Liu
2019-04-17 9:56 ` [Xen-devel] " Wei Liu
2019-04-17 10:41 ` Hypervisor build can't work without `python` (Was: Re: Xen commit 9b0bc91b3 possibly removed too much info from README) Wei Liu
2019-04-17 10:41 ` [Xen-devel] " Wei Liu
2019-04-17 10:44 ` Andrew Cooper
2019-04-17 10:44 ` [Xen-devel] " Andrew Cooper
2019-04-17 10:57 ` Wei Liu
2019-04-17 10:57 ` [Xen-devel] " Wei Liu
2019-04-17 10:58 ` Andrew Cooper
2019-04-17 10:58 ` [Xen-devel] " Andrew Cooper
2019-04-17 11:01 ` Juergen Gross
2019-04-17 11:01 ` [Xen-devel] " Juergen Gross
2019-04-17 11:03 ` Wei Liu
2019-04-17 11:03 ` [Xen-devel] " Wei Liu
2019-04-17 11:15 ` Andrew Cooper
2019-04-17 11:15 ` [Xen-devel] " Andrew Cooper
2019-04-17 11:16 ` Wei Liu
2019-04-17 11:16 ` [Xen-devel] " Wei Liu
2019-04-17 11:23 ` Andrew Cooper
2019-04-17 11:23 ` [Xen-devel] " Andrew Cooper
2019-04-17 11:26 ` Wei Liu
2019-04-17 11:26 ` [Xen-devel] " Wei Liu
2019-04-17 11:43 ` Juergen Gross
2019-04-17 11:43 ` [Xen-devel] " Juergen Gross
2019-04-17 11:53 ` Andrew Cooper
2019-04-17 11:53 ` [Xen-devel] " Andrew Cooper
2019-04-17 12:44 ` Juergen Gross
2019-04-17 12:44 ` [Xen-devel] " Juergen Gross
2019-04-17 14:51 ` Wei Liu
2019-04-17 14:51 ` [Xen-devel] " Wei Liu
2019-04-19 6:07 ` Kevin Buckley
2019-04-19 6:07 ` [Xen-devel] " Kevin Buckley
2019-04-20 4:59 ` Kevin Buckley
2019-04-20 4:59 ` [Xen-devel] " Kevin Buckley
[not found] ` <584ACCED020000078E2C01CD@prv1-mh.provo.novell.com>
[not found] ` <D1DA3F7202000045A293CED3@prv1-mh.provo.novell.com>
[not found] ` <960CB533020000B48E2C01CD@prv1-mh.provo.novell.com>
[not found] ` <D1E23F7802000079A293CED3@prv1-mh.provo.novell.com>
[not found] ` <48D5F043020000E137554D14@prv1-mh.provo.novell.com>
[not found] ` <14AB34BE020000728E2C01CD@prv1-mh.provo.novell.com>
[not found] ` <9A8B94880200008537554D14@prv1-mh.provo.novell.com>
[not found] ` <A9FA5B7C02000009A293CED3@prv1-mh.provo.novell.com>
2019-04-25 11:32 ` Jan Beulich
2019-04-25 11:32 ` [Xen-devel] " Jan Beulich
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='CABwOO=cyX0PcuvbfYu1ZyN384604sT2HPAoJR+cknFqWH-e7PQ@mail.gmail.com' \
--to=kevin.buckley.ecs.vuw.ac.nz@gmail.com \
--cc=andrew.cooper3@citrix.com \
--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.