xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@eu.citrix.com>
To: MaoXiaoyun <tinnycloud@hotmail.com>
Cc: xen devel <xen-devel@lists.xensource.com>,
	"james.harper@bendigoit.com.au" <james.harper@bendigoit.com.au>
Subject: RE: [GIT/PATCH 0/5] Re: unfair servicing of DomU vbd requests
Date: Fri, 4 Mar 2011 07:21:29 +0000	[thread overview]
Message-ID: <1299223289.9486.8.camel@localhost.localdomain> (raw)
In-Reply-To: <BLU157-w14178C1B0ED728CD9D79FCDAC20@phx.gbl>

On Fri, 2011-03-04 at 07:12 +0000, MaoXiaoyun wrote:
> I've tried to clone, but confront this error,  did I do right?

Your command will try and clone my default branch, which I'm not sure I
have configured (I don't really want one since no branch is particularly
special in my tree).

I would recommend that instead of completely cloning a fresh tree for
each tree you are interested in that you just add a new remote to your
existing tree, which could be a clone of e..g xen.git or Linus' tree.

e.g:

Once:
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
$ cd linux-2.6

Then for each new tree you are interested in:
linux-2.6$ git remote add ianc git://xenbits.xen.org/people/ianc/linux-2.6.git
linux-2.6$ git fetch ianc
[...pulls in updates from ianc...]
linux-2.6$ git log ianc/irq-fairness

etc. See "git remote --help" for more info.

Since my irq-fairness branch likely doesn't stand alone you will
probably need to merge it into your current 2.6.38 based head (something
like Konrad's 2.6.38 branch for example). e.g.

linux-2.6$ git merge ianc/irq-fairness

Alternatively (and better) you can pull a single remote branch and merge
it into your current head. e.g.
linux-2.6$ git pull git://xenbits.xen.org/people/ianc/linux-2.6.git irq-fairness

Compared with the git merge approach this creates a more informative
automated merge commit log.

The arguments to git pull are taken literally from the pull request:
> > > The following changes since commit c5ae07bb307b658c8458f29ca77d237aec0f9327:
> > > Ian Campbell (1):
> > > xen: events: remove dom0 specific xen_create_msi_irq
> > > 
> > > are available in the git repository at:
> > > 
> > > git://xenbits.xen.org/people/ianc/linux-2.6.git irq-fairness

Ian.

  reply	other threads:[~2011-03-04  7:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AEC6C66638C05B468B556EA548C1A77D01C55BC6@trantor>
2011-03-04  7:12 ` [GIT/PATCH 0/5] Re: unfair servicing of DomU vbd requests MaoXiaoyun
2011-03-04  7:21   ` Ian Campbell [this message]
2011-03-04  9:59     ` MaoXiaoyun
2011-03-04 10:06       ` Ian Campbell
2011-03-07  3:37         ` MaoXiaoyun
2011-03-07  8:09           ` Ian Campbell
2011-03-07 10:20             ` MaoXiaoyun
2011-03-08  2:04 ` MaoXiaoyun
2011-03-08  2:22   ` James Harper
     [not found]   ` <AEC6C66638C05B468B556EA548C1A77D01C55D47@trantor>
2011-03-09  5:38     ` MaoXiaoyun
2011-03-03  8:30 Keir Fraser
2011-03-03 17:09 ` [GIT/PATCH 0/5] " Ian Campbell
2011-03-04  8:40   ` John Weekes
2011-03-04  9:15     ` Ian Campbell
2011-03-07 19:33       ` John Weekes

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=1299223289.9486.8.camel@localhost.localdomain \
    --to=ian.campbell@eu.citrix.com \
    --cc=james.harper@bendigoit.com.au \
    --cc=tinnycloud@hotmail.com \
    --cc=xen-devel@lists.xensource.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 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).