From: Ian Jackson <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: [OSSTEST PATCH] ts-libvirt-build: Cope with keycodemapdb submodule
Date: Fri, 28 Apr 2017 14:39:47 +0100 [thread overview]
Message-ID: <1493386787-12491-1-git-send-email-ian.jackson@eu.citrix.com> (raw)
libvirt.git#02fb15f introduces this new submodule.
Submodules are awkward, and we need them to be explicitly listed.
So add keycodemapdb to the submodulemap in ts-libvirt-build.
Reported-by: Wei Liu <wei.liu2@citrix.com>
Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
---
ts-libvirt-build | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/ts-libvirt-build b/ts-libvirt-build
index 714402b..419f3ec 100755
--- a/ts-libvirt-build
+++ b/ts-libvirt-build
@@ -26,7 +26,8 @@ tsreadconfig();
selectbuildhost(\@ARGV);
builddirsprops();
-our %submodmap = qw(gnulib gnulib);
+our %submodmap = qw(gnulib gnulib
+ keycodemapdb keycodemapdb);
our $submodules;
sub libvirtd_init ();
--
2.1.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
reply other threads:[~2017-04-28 13:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1493386787-12491-1-git-send-email-ian.jackson@eu.citrix.com \
--to=ian.jackson@eu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).