Re: [Xen-devel] [PATCH v2 3/4] Clone and build upstream Qemu by default

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Fri, 2011-09-09 at 06:18 -0400, Stefano Stabellini wrote:
> On Thu, 8 Sep 2011, Ian Campbell wrote:
> > On Thu, 2011-09-08 at 13:47 -0400, stefano.stabellini@xxxxxxxxxxxxx
> > wrote:
> > > Signed-off-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
> > > 
> > > diff -r 80ba2c7abbd2 Config.mk
> > > --- a/Config.mk   Thu Sep 08 16:59:19 2011 +0000
> > > +++ b/Config.mk   Thu Sep 08 17:18:48 2011 +0000
> > > @@ -192,6 +192,10 @@ else
> > >  QEMU_REMOTE=git://xenbits.xensource.com/qemu-xen-unstable.git
> > >  endif
> > >  
> > > +# Only available through the git protocol at the moment
> > > +QEMU_UPSTREAM_URL ?= git://xenbits.xen.org/people/sstabellini/qemu-dm.git
> > 
> > Just a nit, but we should arrange to have a "proper" tree rather than
> > a /people/... one for the default tree. e.g. to allow automated testing
> > to automatically push etc.
> 
> Like Linus said, thanks to distributed version control systems, it
> doesn't actually matter where the repository is anymore :-)

In technical terms perhaps not but for practical reasons we want the
default tree which we point people to live next to all the other default
trees, otherwise they won't be able to reliably find it the sea of suchs
trees which we will eventually have under /people/. Linus' tree being
just one of a thousand trees under git.kernel.org was always a pain
IMHO.

We also want to test and automatically push a tested branch like we do
for the other trees and we really don't want to give the test system
access to your (or anyone else's) xenbits account.

With the number of trees which we have now we should maybe consider
putting each branch in a subdir:
        [/staging]/xen-unstable/xen.hg
                               /qemu-xen.hg
                               /qemu.git
                               /seabios.git 
        [/staging]/xen-4.2/xen.hg
                          /...

? (staging could also go after the dir I suppose)

Ian.



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel