From mboxrd@z Thu Jan  1 00:00:00 1970
From: Alex Williamson <alex.williamson@hp.com>
Subject: Re: Re: [Xen-changelog] [xen-unstable] [IA64] fix
	xencomm_handle_is_null().
Date: Thu, 16 Nov 2006 11:08:19 -0700
Message-ID: <1163700499.5529.9.camel@lappy>
References: <E1Gk8pJ-0007ef-Tr@xenbits.xensource.com>
	<1163692542.26011.14.camel@basalt>
Mime-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <1163692542.26011.14.camel@basalt>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: xen-ia64-devel@lists.xensource.com, xen-devel@lists.xensource.com, xen-ppc-devel <xen-ppc-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

On Thu, 2006-11-16 at 09:55 -0600, Hollis Blanchard wrote:
> 
> I think I'm missing something. Why did IA64 fork xencomm?
> 
> I distinctly remember having conversations about sharing the code, which
> is obviously the right thing to do.

   Because Tristan believed the resulting amount of shared code would
actually be very small (1 file) and we wanted to get his work into the
tree before he left Bull.  We can still work to share as much as
possible even with the code split.  Thanks,

	Alex

-- 
Alex Williamson                             HP Open Source & Linux Org.