[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [PATCH] Re: [Xen-devel] New release candidate for Xen 4.0.1
One result of this process is that it makes it difficult
to see changes via the xen-changelog mailing list as
the pull by Keir into xen-unstable just shows up as
a Merge, without any of the changeset title or log detail.
Any way to fix this? If necessary, by adding the
staging/xen-unstable-tools.hg tree to the changelog
> -----Original Message-----
> From: Keir Fraser [mailto:keir.fraser@xxxxxxxxxxxxx]
> Sent: Wednesday, July 21, 2010 4:23 AM
> To: M A Young
> Cc: Ian Campbell; xen-devel@xxxxxxxxxxxxxxxxxxx; Stefano Stabellini
> Subject: Re: [PATCH] Re: [Xen-devel] New release candidate for Xen
> On 21/07/2010 10:42, "M A Young" <m.a.young@xxxxxxxxxxxx> wrote:
> > On Tue, 20 Jul 2010, Keir Fraser wrote:
> >> Shouldn't this be in xen-unstable first, and then backported in the
> >> way?
> > If that is the normal process then yes. I haven't checked whether
> > bug exists in xen-unstable, but a quick glance at the Makefile I am
> > patching suggests that it probably does.
> The precise process for toolset patches now is that they get applied to
> http://xenbits.xen.org/staging/xen-unstable-tools.hg by Ian Jackson or
> Stefano Stabellini. I merge that tree into main xen-unstable.hg nearly
> day. Then, for 4.0.x and 3.4.x stable branches, Ian and Stefano
> patches for backport from xen-unstable.
> -- Keir
> > Michael Young
> Xen-devel mailing list
Xen-devel mailing list