All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Jackson <ian.jackson@eu.citrix.com>
To: "Hao, Xudong" <xudong.hao@intel.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	Wei Liu <wei.liu2@citrix.com>, Jan Beulich <JBeulich@suse.com>
Subject: Re: qemu-traditional build problem for Xen 4.7.0 RC6
Date: Fri, 17 Jun 2016 15:31:01 +0100	[thread overview]
Message-ID: <22372.2469.897694.164758@mariner.uk.xensource.com> (raw)
In-Reply-To: <B8376D2DEA074F45BA033984477C453E034C7B43@shsmsx102.ccr.corp.intel.com>

Hao, Xudong writes ("RE: [Xen-devel] qemu-traditional build problem for Xen 4.7.0 RC6"):
> Actually it's not compile error, it's a repo clone issue. Error log is:
> 
> ...
> Initialized empty Git repository in /home/www/builds_xen_unstable/xen-src-xen-4.7.0-rc6-20160616/tools/qemu-xen-traditional-dir-remote.tmp/.git/
> fatal: reference is not a tree: 698d6d6f8d095edadb0c23612b552a89dd3eee4c
> make[2]: *** [qemu-xen-traditional-dir-find] Error 128
> ...
> 
> The issue get root caused and resolved now. 
> The failure is that we set up a local repo mirror for qemu-xen-traditional, but the mirror only sync "master" branch, not include "stable-4.7" branch, so commit 698d6d6* didn't be identified when doing checkout. 

OK, thanks for clearing that up.

Indeed, the "master" branch won't (in general) contain all the
relevant commits, because stable branches like 4.7 do diverge.

Regards,
Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

      reply	other threads:[~2016-06-17 14:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-17  3:11 qemu-traditional build problem for Xen 4.7.0 RC6 Hao, Xudong
2016-06-17  7:58 ` Jan Beulich
2016-06-17  8:46   ` Hao, Xudong
2016-06-17 14:31     ` Ian Jackson [this message]

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=22372.2469.897694.164758@mariner.uk.xensource.com \
    --to=ian.jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    --cc=xudong.hao@intel.com \
    /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.