From: Zachary Amsden <zach@vmware.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Chris Wright <chrisw@sous-sol.org>, Andi Kleen <ak@muc.de>,
Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
Virtualization Mailing List <virtualization@lists.osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/9] Vmi fix highpte
Date: Fri, 02 Mar 2007 23:58:22 -0800 [thread overview]
Message-ID: <45E92A9E.6030108@vmware.com> (raw)
In-Reply-To: <45E9273A.4040300@goop.org>
Jeremy Fitzhardinge wrote:
>
> I can deal with the change going into -git, but it does seem awkward
> knowing that it is the wrong change and it will be replaced by something
> else almost immediately.
>
Well, it is not quite wrong - it is appropriate for -git. That it will
be replaced soon is a minor thing, as long as we can work together to
make sure your patches are unaffected.
> My main concern is that the Xen patch queue is complex enough as-is, and
> I've been trying hard to remove dependencies on other uncommitted
> patches. It's doubly complex because I'm not really sure if I'm
> targeting Andrew or Andi's tree as a base, though at the moment -git
> seems to work either way.
>
> J
>
Believe me, I understand the complexities of dealing with -mm, -git, and
-i386 trees. It's not just doubly complex, its triply so. I believe
the best approach is to make it easiest on the maintainers. So the
patch stream I am uploading through -mm, -i386, to -git does not
conflict with the Xen patch queue as long as we make sure the next
bundle to those same trees applies clean. Again, I broke the Xen patch
queue in -mm, and for that I am sorry. I will help you re-integrate
against the VMI patches I sent out, as I broke your code, I will help
fix it. And we both have a tree to work off from, which makes it rather
easy to work together ;)
Cheers,
Zach
----
Sutra I.2 - interruptah chittavritti nirodhah
prev parent reply other threads:[~2007-03-03 7:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-02 2:54 [PATCH 4/9] Vmi fix highpte Zachary Amsden
2007-03-02 3:08 ` Jeremy Fitzhardinge
2007-03-02 3:39 ` Jeremy Fitzhardinge
2007-03-02 6:24 ` Zachary Amsden
2007-03-02 6:29 ` Jeremy Fitzhardinge
2007-03-02 6:31 ` Zachary Amsden
2007-03-02 6:45 ` Jeremy Fitzhardinge
2007-03-02 9:53 ` Zachary Amsden
2007-03-02 16:55 ` Jeremy Fitzhardinge
2007-03-03 7:17 ` Zachary Amsden
2007-03-03 7:43 ` Jeremy Fitzhardinge
2007-03-03 7:58 ` Zachary Amsden [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=45E92A9E.6030108@vmware.com \
--to=zach@vmware.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=virtualization@lists.osdl.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).