xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Wim ten Have <whaveten@gmail.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
	Wei Liu <wei.liu2@citrix.com>, Safa Hamza <safahamza1@gmail.com>
Subject: Re: error while compiling Xen from the source
Date: Wed, 15 Jun 2016 12:34:13 -0400	[thread overview]
Message-ID: <20160615163413.GA3230@char.us.oracle.com> (raw)
In-Reply-To: <CAB4W_ZymfeNsW3Jbu8jVBKX6GQgiWMRUQpFRFaxdE+a6yWWW2g@mail.gmail.com>

On Wed, Jun 15, 2016 at 05:26:52PM +0200, Wim ten Have wrote:
> Running F23 here seemed to go trough good with above URL (making up much
> for my environment).
> 
> The only part causing me trouble is page specific direction setting the
> branch:
> 
> $ cd xen;
> *git checkout -b staging staging*

It loooks to have missed the 'origin' part.

One usually does 'git checkout origin/staging -b staging'

> 
> 
> Instead I did here (and think it should be)
> 
> $ cd xen; *git checkout -b staging*
> 
> Example:
> 
> 
> <wtenhave@kruimel:69> git checkout -b staging
> Switched to a new branch 'staging'

The -b creates a new branch. And you called it staging.
But it may have nothing to do with the origin staging.

git branch -r

gives a good idea of the remote branches (so the ones you pull from)
vs the local ones:

git branch

Usually when you clone a tree it will clone the 'master' branch.
So I think your 'staging' is at the same commit as the 'master'.
If you want the latest, you would need to do:

git branch -d staging
git checkout origin/staging -b staging


P.S.
The Git Manual is very solid.
> 
> 
> On Wed, Jun 15, 2016 at 5:07 PM, Konrad Rzeszutek Wilk <
> konrad.wilk@oracle.com> wrote:
> 
> > On Fri, Jun 10, 2016 at 04:03:30PM +0100, Safa Hamza wrote:
> > > i'm really confused
> > > i build xen from the source in pc running ubuntu mate but while trying to
> >
> > Take a look at
> > http://wiki.xenproject.org/wiki/Compiling_Xen_From_Source#Build_Dependencies_-_Debian_.2F_Ubuntu
> > and follow the directions there.
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xen.org
> > http://lists.xen.org/xen-devel
> >

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

  parent reply	other threads:[~2016-06-15 16:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-02 15:22 error while compiling Xen from the source Safa Hamza
2016-06-02 15:26 ` Wei Liu
2016-06-03 15:21   ` Safa Hamza
2016-06-03 15:23     ` Wei Liu
2016-06-10 12:03       ` Safa Hamza
2016-06-10 13:23         ` Wei Liu
2016-06-10 13:53           ` Safa Hamza
2016-06-10 14:25             ` Safa Hamza
2016-06-10 14:33               ` Wei Liu
2016-06-10 14:41                 ` Safa Hamza
2016-06-10 14:47                   ` Wei Liu
2016-06-10 15:03                     ` Safa Hamza
2016-06-10 15:11                       ` Wei Liu
2016-06-15 15:07                       ` Konrad Rzeszutek Wilk
2016-06-15 15:26                         ` Wim ten Have
2016-06-15 16:11                           ` Wei Liu
2016-06-15 16:34                           ` Konrad Rzeszutek Wilk [this message]
2016-06-15 17:11                             ` Wim ten Have
2016-06-15 15:32 ` Meng Xu

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=20160615163413.GA3230@char.us.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=safahamza1@gmail.com \
    --cc=wei.liu2@citrix.com \
    --cc=whaveten@gmail.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).