From: Dario Faggioli <dario.faggioli@citrix.com>
To: <konrad@darnok.org>
Cc: David Vrabel <david.vrabel@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jan Beulich <JBeulich@suse.com>, Yechen Li <lccycc123@gmail.com>
Subject: Re: [Xen-devel] [PATCH v1][RFC] drivers/xen, balloon driver numa support in kernel
Date: Tue, 13 Aug 2013 21:00:27 +0200 [thread overview]
Message-ID: <1376420427.19076.11.camel@Abyss> (raw)
In-Reply-To: <CAPbh3ru-gq0oL-MFbXmWDWOLwXVqZSbKUSJbotBJVy7OLYgKbw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2121 bytes --]
On mar, 2013-08-13 at 09:18 -0400, Konrad Rzeszutek Wilk wrote:
> On Tue, Aug 13, 2013 at 8:53 AM, David Vrabel <david.vrabel@citrix.com> wrote:
> > On 12/08/13 21:26, Dario Faggioli wrote:
> >>
> >> Mmm... Is that the case? I tried to apply it there and I have one failed
> >> hunk (#12). Anyway, could you please rebase it on the tip of some
> >> relevant git tree?
> >>
> >> Linus' tree would be fine, I guess:
> >>
> >> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git
> >
> > This is the one I use for most of my development work. I wouldn't use a
> > subsystem specific tree unless there were specific conflicts to resolve
> > before hand.
>
> Which we do:
>
> commit cd9151e26d31048b2b5e00fd02e110e07d2200c9
> Author: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> Date: Sun Aug 4 15:39:40 2013 +0100
> xen/balloon: set a mapping for ballooned out pages
>
Ok... So, working on Linus' tree on a daily basis, but at lease try to
rebase the changes on top of .../xen/tip.git sounds like a sane enough
workflow to me. :-)
Yechen, would you be fine with something like that?
How familiar are you with concepts like branches, merging and rebasing
in the context of git?
Allow me to give some (pseudo random) pointers:
http://git-scm.com/documentation
http://git-scm.com/book/en/Git-Branching-Basic-Branching-and-Merging
http://git-scm.com/book/en/Git-Branching-Rebasing
http://gitref.org/branching/
http://stackoverflow.com/questions/315911/git-for-beginners-the-definitive-practical-guide
http://sixrevisions.com/resources/git-tutorials-beginners/
http://www.sbf5.com/~cduan/technical/git/
http://www.sbf5.com/~cduan/technical/git/git-2.shtml
http://www.sbf5.com/~cduan/technical/git/git-3.shtml
http://www.sbf5.com/~cduan/technical/git/git-5.shtml
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2013-08-13 19:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 14:13 [PATCH v1][RFC] drivers/xen, balloon driver numa support in kernel Yechen Li
2013-08-12 18:44 ` [Xen-devel] " David Vrabel
2013-08-12 20:14 ` Dario Faggioli
[not found] ` <1376339161.15390.281.camel@Solace>
2013-08-13 12:46 ` Konrad Rzeszutek Wilk
[not found] ` <520A2C52.3000804@citrix.com>
2013-08-13 13:18 ` Konrad Rzeszutek Wilk
2013-08-13 19:00 ` Dario Faggioli [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=1376420427.19076.11.camel@Abyss \
--to=dario.faggioli@citrix.com \
--cc=JBeulich@suse.com \
--cc=david.vrabel@citrix.com \
--cc=konrad@darnok.org \
--cc=lccycc123@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xen.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