[U-Boot] [OE-core] [PATCH] u-boot: Upgrade to 2017.11 release

[Ladislav Michl]

On Thu, Nov 16, 2017 at 04:34:51PM -0200, Otavio Salvador wrote:
> On Thu, Nov 16, 2017 at 4:21 PM, Marek Vasut <marex at denx.de> wrote:
> > On 11/16/2017 01:02 PM, Otavio Salvador wrote:
> >> On Thu, Nov 16, 2017 at 6:12 AM, Marek Vasut <marex at denx.de> wrote:
> >>> On 11/15/2017 05:47 PM, Stefan Agner wrote:
> >>>> On 2017-11-14 19:32, Otavio Salvador wrote:
> >>>>> This upgrades the U-Boot from 2017.09 to 2017.11 release.
> >>>>
> >>>> You might encounter this when building fw_printenv/setenv tools alone:
> >>>>
> >>>> https://lists.denx.de/pipermail/u-boot/2017-November/311505.html
> >>>
> >>> [...]
> >>>
> >>>>>  SRC_URI = "git://git.denx.de/u-boot.git \
> >>>>>      file://MPC8315ERDB-enable-DHCP.patch \
> >>> I also see that the number of out-of-tree patches didn't change since
> >>> last time, even though I complained about it ... why are these patches
> >>> still here ?
> >>
> >> Because you are the maintainer and didn't do your duty.
> >
> > And what duty is that exactly ? I at least inquired about the status of
> > these patches and reviewed them [1] (the other was not submitted to ML
> > yet and submitter is not responding), so do you have anything else in mind ?
> >
> > [1] https://marc.info/?l=u-boot&m=150533817907015&w=2
> 
> Good, so I don't see the reason for the question.
> 
> I did upgrade the recipe and tested. It didn't have patches merged so
> there is nothing I can do. 

Sure there is. Merging patches does not happen automagically, so it is
your (or whoevers, but definitely not maintainers) responsibility to check
upstream status and eventually resubmit.

> You being the maintainer can keep an eye here.

No. Maintainer's job is mostly rejecting poor quality patches and merging
those properly submited, tested and described. What you are asking for
is ussually called babysitting.

> >>> I also see that the number of out-of-tree patches didn't change since
> >>> last time, even though I complained about it ... why are these patches
> >>> still here ?
> 
> Your question was pointless. So instead of "complain" as you said,
> make sure those are merged.

While I see no reason U-Boot list was cc'ed on this patch, your attitude
is almost perfect example how _not_ to do opensource development.

Best regards,
	ladis