All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: Yuji Shimada <shimada-yxb@necst.nec.co.jp>,
	Xen Developers <xen-devel@lists.xensource.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Keir Fraser <Keir.Fraser@eu.citrix.com>,
	"Zhai, Edwin" <edwin.zhai@intel.com>
Subject: Re: Repositories and build system
Date: Thu, 7 May 2009 17:51:16 +0100	[thread overview]
Message-ID: <4A031184.8030802@eu.citrix.com> (raw)
In-Reply-To: <d432ea90-6185-4406-a61b-71558256a64b@default>

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.

  parent reply	other threads:[~2009-05-07 16:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-28  7:34 [PATCH] [Xend] Fix HVM PCI hot removal failure Zhai, Edwin
2009-04-28  7:52 ` Keir Fraser
2009-04-28  8:18   ` Zhai, Edwin
2009-04-28  9:17     ` Keir Fraser
2009-04-28  9:33       ` Zhai, Edwin
2009-04-28 10:38         ` Stefano Stabellini
2009-04-29 15:41           ` Repositories and build system Ian Jackson
2009-04-29 16:38             ` Dan Magenheimer
2009-04-29 16:56               ` Ian Jackson
2009-04-29 17:40                 ` Dan Magenheimer
2009-04-29 18:06                   ` Keir Fraser
2009-05-07 16:51                   ` Stefano Stabellini [this message]
2009-05-07 17:00                     ` Brendan Cully
2009-05-07 18:17                       ` Keir Fraser
2009-04-28 12:17         ` [PATCH] [Xend] Fix HVM PCI hot removal failure Keir Fraser

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=4A031184.8030802@eu.citrix.com \
    --to=stefano.stabellini@eu.citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=Keir.Fraser@eu.citrix.com \
    --cc=dan.magenheimer@oracle.com \
    --cc=edwin.zhai@intel.com \
    --cc=shimada-yxb@necst.nec.co.jp \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.