From: Keir Fraser Subject: Re: Repositories and build system Date: Thu, 07 May 2009 19:17:09 +0100 Message-ID: References: <20090507170014.GA30350@kathmandu.van.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20090507170014.GA30350@kathmandu.van.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Brendan Cully , Stefano Stabellini Cc: Yuji Shimada , Dan Magenheimer , Xen Developers , Ian Jackson , "Zhai, Edwin" List-Id: xen-devel@lists.xenproject.org On 07/05/2009 18:00, "Brendan Cully" wrote: >> I agree. >> In fact I think we should start to write in clear letters when a commit >> breaks xen\qemu compatibility, specifying the required changeset in the >> other repository. >> We could formally introduce this practice with the 3.5 development cycle. > > This would certainly be an improvement, but it depends on the > developer always knowing and recording exactly what synchronization is > needed. This doesn't quite jibe with bisect, whose raison d'etre is to > help find problems that went unnoticed for potentially long periods of > time. Even when the hints work, bisection is still quite painful > across two repositories in two different version control systems. We plan to turn on the QEMU_TAG mechanism always after 3.4 is branched, so that by default xen-unstable.hg will always clone a specific version of the qemu git repository. I'm sure it should be then be possible to make bisect update the foreign qemu repo as it goes quite straightforwardly. -- Keir