* master branch of xen.git
@ 2010-08-11 6:38 Jan Beulich
2010-08-11 6:45 ` Jeremy Fitzhardinge
0 siblings, 1 reply; 4+ messages in thread
From: Jan Beulich @ 2010-08-11 6:38 UTC (permalink / raw)
To: Jeremy Fitzhardinge; +Cc: xen-devel@lists.xensource.com
Jeremy,
what's the disposition of the master branch of that tree? It doesn't
seem to have seen any update during the last couple of months,
and it's still 2.6.31-based. Shouldn't this be either what "stable"
is currently (i.e. 2.6.32-based) or match up with Linus' tree (or
the latest released version thereof)?
Jan
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: master branch of xen.git
2010-08-11 6:38 master branch of xen.git Jan Beulich
@ 2010-08-11 6:45 ` Jeremy Fitzhardinge
2010-08-11 6:58 ` Jan Beulich
0 siblings, 1 reply; 4+ messages in thread
From: Jeremy Fitzhardinge @ 2010-08-11 6:45 UTC (permalink / raw)
To: Jan Beulich; +Cc: xen-devel@lists.xensource.com
On 08/10/2010 11:38 PM, Jan Beulich wrote:
> what's the disposition of the master branch of that tree? It doesn't
> seem to have seen any update during the last couple of months,
> and it's still 2.6.31-based. Shouldn't this be either what "stable"
> is currently (i.e. 2.6.32-based) or match up with Linus' tree (or
> the latest released version thereof)?
I keep forgetting to update it. I think of it as a deprecated branch
I'd like to get rid of, since the name is too vague. In principle the
name could be better used for something like "bleeding edge head", but I
think changing its meaning like that would be way too much trouble, so
just dropping it after migrating everything away from it is probably the
best thing to do.
In the meantime, I'll make it the same as xen/stable-2.6.31.x, since
that's more or less what it means. (Likewise, xen/stable is tracking
xen/stable-2.6.32.x at the moment).
I've also just started putting together a (pre-rc)2.6.36-based dom0
branch which will become the development focus soon (leaving 2.6.32
still supported but with backported changes, rather than the current
flow of developing in .32 then forward-porting).
J
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: master branch of xen.git
2010-08-11 6:45 ` Jeremy Fitzhardinge
@ 2010-08-11 6:58 ` Jan Beulich
2010-08-13 0:46 ` Jeremy Fitzhardinge
0 siblings, 1 reply; 4+ messages in thread
From: Jan Beulich @ 2010-08-11 6:58 UTC (permalink / raw)
To: Jeremy Fitzhardinge; +Cc: xen-devel@lists.xensource.com
>>> On 11.08.10 at 08:45, Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> I've also just started putting together a (pre-rc)2.6.36-based dom0
> branch which will become the development focus soon (leaving 2.6.32
> still supported but with backported changes, rather than the current
> flow of developing in .32 then forward-porting).
Wouldn't that be the ideal "master" when it becomes ready?
Jan
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Re: master branch of xen.git
2010-08-11 6:58 ` Jan Beulich
@ 2010-08-13 0:46 ` Jeremy Fitzhardinge
0 siblings, 0 replies; 4+ messages in thread
From: Jeremy Fitzhardinge @ 2010-08-13 0:46 UTC (permalink / raw)
To: Jan Beulich; +Cc: xen-devel@lists.xensource.com
On 08/10/2010 11:58 PM, Jan Beulich wrote:
>>>> On 11.08.10 at 08:45, Jeremy Fitzhardinge<jeremy@goop.org> wrote:
>> I've also just started putting together a (pre-rc)2.6.36-based dom0
>> branch which will become the development focus soon (leaving 2.6.32
>> still supported but with backported changes, rather than the current
>> flow of developing in .32 then forward-porting).
> Wouldn't that be the ideal "master" when it becomes ready?
Eventually, but it should be retired from its current role for a while.
J
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2010-08-13 0:46 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-08-11 6:38 master branch of xen.git Jan Beulich
2010-08-11 6:45 ` Jeremy Fitzhardinge
2010-08-11 6:58 ` Jan Beulich
2010-08-13 0:46 ` Jeremy Fitzhardinge
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).