Re: [Xen-devel] [PATCH 0/9] xen: build fixes with gcc5 and binutils 2.25.0

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 06.02.16 at 02:48, <mcgrof@xxxxxxxx> wrote:
> On Fri, Nov 20, 2015 at 9:47 AM, Luis R. Rodriguez
> <mcgrof@xxxxxxxxxxxxxxxx> wrote:
>> From: "Luis R. Rodriguez" <mcgrof@xxxxxxxx>
>>
>> Here's a slew of build fixes as well as build warning fixes
>> required when using the latest build tools, at least gcc 5 and
>> binutils 2.25.0.
> 
> One good reason for some folks to get discouraged to work with Xen:
> 
> Patches for fixes on builds last ages to get merged
> 
> In this case Mark Pryor <pryorm09@xxxxxxxxx> reported an issue and
> offered a fix on October 8, 2015 [0]. That did not go in as Jan noted
> it was probably not the right fix. Last year in November I provided
> what I think is a proper replacement set which I think addressed Jan's
> concerns.

A link to your submission instead of Mark's, which has been given
feedback on, would have been more helpful.

> ***Four*** months later and Xen still does not compile with the latest
> and greatest. I have to go digging out in my git basement somewhere
> some fixes I last used to build Xen to try to test some new
> features...
> 
> What's up folks? How can this process be made smoother, did I do
> something wrong, what can I do to help better? What can you do to help
> ensure these types of things don't fall through the cracks.

Patch 1 should have gone through SeaBIOS and then a backport
should have been requested. Patch 2 should equally have gone
through upstream qemu, and then a backport be requested. I
won't continue for the other ones.

Neither (apart from 4 and 5, which do so indirectly, referencing
something that isn't even a repo) indicates (in the title) what
component it's against.

And nothing in the entire series seems to fall into my areas of
responsibility, so I can't see why both the original series and
this mail was addressed to me. 

Please - don't complain about things not getting accepted if
you don't even follow basic submission rules.

Jan


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