| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] Repositories and build system
|
To: |
Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> |
|
Subject: |
Re: [Xen-devel] Repositories and build system |
|
From: |
Brendan Cully <brendan@xxxxxxxxx> |
|
Date: |
Thu, 7 May 2009 10:00:14 -0700 |
|
Cc: |
Yuji Shimada <shimada-yxb@xxxxxxxxxxxxxxx>, Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, Xen Developers <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Zhai, Edwin" <edwin.zhai@xxxxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, Keir Fraser <Keir.Fraser@xxxxxxxxxxxxx> |
|
Delivery-date: |
Thu, 07 May 2009 10:00:47 -0700 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<4A031184.8030802@xxxxxxxxxxxxx> |
|
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
|
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
|
List-post: |
<mailto:xen-devel@lists.xensource.com> |
|
List-subscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
|
List-unsubscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
|
Mail-followup-to: |
stefano.stabellini@xxxxxxxxxxxxx, dan.magenheimer@xxxxxxxxxx, shimada-yxb@xxxxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, Ian.Jackson@xxxxxxxxxxxxx, Keir.Fraser@xxxxxxxxxxxxx, edwin.zhai@xxxxxxxxx |
|
References: |
<d432ea90-6185-4406-a61b-71558256a64b@default> <4A031184.8030802@xxxxxxxxxxxxx> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
|
User-agent: |
Mutt/1.5.19 (2009-04-29) |
On Thursday, 07 May 2009 at 17:51, Stefano Stabellini wrote:
> Dan Magenheimer wrote:
>
> >>> "Pull and build all latest known stable components
> >>> that work with xen-unstable changeset 19314"
> >> That would require formal, machine-readable tracking of the
> >> inter-version dependencies. Since at the moment we can't reliably
> >> accidentally avoid introducing cross-version breakage I don't think we
> >> can reliably avoid buggy metadata either.
> >
> > Understood. But it is a big loss to be unable to do a bisect
> > search for a bug. With the proliferation of repositories
> > and components, it may become necessary to impose some discipline
> > to avoid the introduction of (undocumented) locksteps.
> >
>
>
> 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.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home