Re: [Xen-devel] [PATCH] tools/seabios: override $(PYTHON)

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Tue, 2012-02-21 at 15:31 +0000, Ian Jackson wrote:
> Ian Campbell writes ("Re: [Xen-devel] [PATCH] tools/seabios: override 
> $(PYTHON)"):
> > On Tue, 2012-02-21 at 15:14 +0000, Ian Jackson wrote:
> > > Ian Campbell writes ("Re: [Xen-devel] [PATCH] tools/seabios: override 
> > > $(PYTHON)"):
> > > > On Tue, 2012-02-21 at 12:34 +0000, Ian Jackson wrote:
> > > > > Why not make "master" be equal to the SEABIOS_UPSTREAM_TAG in
> > > > > xen-unstable's Config.mk ?  That's what I do with
> > > > > qemu-xen-unstable.git.
> > > > 
> > > > That would make master rebasing. I'm happy to do that if there is
> > > > consensus that it is ok.
> > > 
> > > Wait, you're rewinding SEABIOS_UPSTREAM_TAG ?  That's quite exciting.
> > 
> > SEABIOS_UPSTREAM_TAG is tracking an upstream stable branch. When they
> > release a new stable release we will want to switch to that, but that
> > will not be a fast-forward.
> 
> Hmm.  Well as to the question of what "master" should be:
> 
> If it's anything useful at all,

(which I'm not personally convinced of, but I seem to be in the minority
so I shall try and make it mean something)

> it needs to be what you would need to
> edit to change the result of the Xen build.  So either it must be
> .._TAG

I'll choose this option. I'll also edit the repo description to make it
clear that all branches are rebasing.

>  or it must be some fast-forwarding branch constructed from the
> series of _TAG values.  (Ie, a branch whose commits correspond 1:1
> with _TAG values, each commit on the master branch having the previous
> master commit as its left parent and the _TAG, which determines the
> contents, as the right parent.)

I think I'd inevitably end up cocking this scheme up, especially given
the expected frequency of seabios updates (e.g. v. low).

Ian.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel