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

Re: [Xen-devel] tags in backport commits



>>> On 13.06.17 at 19:41, <sstabellini@xxxxxxxxxx> wrote:
> On Tue, 13 Jun 2017, George Dunlap wrote:
>> On 13/06/17 08:28, Jan Beulich wrote:
>> > Furthermore - who would you mean to create these tags? In the
>> > end I think it should be the person responsible for the respective
>> > parts of the stable trees to decide if and how far such backports
>> > ought to occur, so neither the person submitting the patch nor
>> > the person committing the patch are in the position to give more
>> > than a hint here (again speaking against using such tags for
>> > automation).
>> 
>> We could require that the "stable" tag be acked by any stable tree
>> maintainers that it affects.
> 
> Yes, that is where CC: stable@xxxxxxxxxxxxxx comes into play. The people
> at stable@xxxxxxxxxxxxxx should ack or request a chance to the
> backporting info. The first step would be to create a mailing list for
> that.

Isn't Linux'es stable@ a fake address? I'm not really fancying getting
yet another copy of patches through such a new alias or list, so I'd
expect this to be a fake address in our case too.

Jan


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

 


Rackspace

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