Re: [PATCH] Re: New release candidate for Xen 4.0.1

[Keir Fraser <keir.fraser@eu.citrix.com>]

Er, no. There's still one email per changeset. You can ignore the merge
changesets: they're all trivial auto merges, and I'm not sure why they end
up with an associated diff, it must be how mercurial consolidates and merges
a branch.

 -- Keir

On 21/07/2010 17:30, "Dan Magenheimer" <dan.magenheimer@oracle.com> wrote:

> 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
> mailing list?
> 
>> -----Original Message-----
>> From: Keir Fraser [mailto:keir.fraser@eu.citrix.com]
>> Sent: Wednesday, July 21, 2010 4:23 AM
>> To: M A Young
>> Cc: Ian Campbell; xen-devel@lists.xensource.com; Stefano Stabellini
>> Subject: Re: [PATCH] Re: [Xen-devel] New release candidate for Xen
>> 4.0.1
>> 
>> On 21/07/2010 10:42, "M A Young" <m.a.young@durham.ac.uk> wrote:
>> 
>>> On Tue, 20 Jul 2010, Keir Fraser wrote:
>>> 
>>>> Shouldn't this be in xen-unstable first, and then backported in the
>> usual
>>>> way?
>>> 
>>> If that is the normal process then yes. I haven't checked whether
>> this
>>> 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
>> every
>> day. Then, for 4.0.x and 3.4.x stable branches, Ian and Stefano
>> nominate
>> patches for backport from xen-unstable.
>> 
>>  -- Keir
>> 
>>> Michael Young
>> 
>> 
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel