[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] raisin: update defaults according to the current content of Config.mk

On Tue, 12 May 2015, Ian Campbell wrote:
> On Tue, 2015-05-12 at 10:25 +0100, George Dunlap wrote:
> > On 05/12/2015 10:16 AM, Stefano Stabellini wrote:
> > > Signed-off-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
> > 
> > What's the purpose of doing this?  In particular it seems like having to
> > manually update the changesets as we go along is going to be a big pain
> > in the neck.  There shouldn't be a need to keep raisin.git and xen.git
> > in such close synchrony.
> The intent is to replace the tracking we currently do in xen.git with
> tracking in raisin.git, not to keep the two in sync. It'll have to run
> alongside until we actually remove that stuff from xen.git though.
> For example, we do not want to just track seabios master, that is a
> development version. I (as maintainer) want to track seabios releases
> which are tested against Xen, especially for a release.
> OVMF and qemu-trad are also similarly managed in Config.mk.
> Stefano, I think it would be good to also import the little comment
> snippet associated with the manually maintained revisions in Config.mk.


> For the other branches Config.mk automatically tracks the outputs of the
> various osstest push gates. It looks like raisin's defconfig already
> mostly does that.
> I think we should consider whether for libvirt raisin should be using
> git://xenbits.xen.org/libvirt.git#xen-tested-master by default.

Sounds like a good idea

> We should also consider for linux whether to use our tested tree on
> xenbits, but I think that is less likely to be desirable.

The Linux tree tested by osstest is based on 3.14, a bit too old for
raisin, I think.

> BTW, the canonical URL for Linus' tree is
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git not
> what is currently in defconfig.

I'll fix it

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.