From: Martin Jansa <martin.jansa@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Patch merge process
Date: Wed, 2 Sep 2015 22:29:03 +0200 [thread overview]
Message-ID: <20150902202903.GA29340@jama> (raw)
In-Reply-To: <1441179093.24871.49.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 2221 bytes --]
On Wed, Sep 02, 2015 at 08:31:33AM +0100, Richard Purdie wrote:
> I've not said it is a bad thing. What I'm asking is whether more people
> can devote a bit of time to fixing things which aren't their immediate
> problem?
Part of this problem is that sometimes it's almost too pain-full to get
some changes merged for issues which are my immediate problem that in
the end I have to implement them in our fork anyway, We cannot wait
months until it's merged and then few more months to get it backported
into older releases we're using.
So now it's usually fix it in the fork first and then if it doesn't look
controversial, try to upstream it, but the with much lower priority.
like:
http://lists.openembedded.org/pipermail/openembedded-core/2014-March/091222.html
http://patchwork.openembedded.org/patch/76601/ sent July 2014, went in on Mar 9 2015
I'm not saying it's yours or Ross's or anyone's fault. Or I'm faulty as well
with rejecting meta-oe patches until they pass my "bitbake world" tests
and sometimes it can be very hard to reproduce the issues found there.
But I understand the pain and frustration of contributors and agree with
Khem that in long term we have to do something about it or will start
loosing contributions even faster.
> For example, Martin mentioned problems with errors.yp.org.
> There are a ton of open issues with errors.yp.org (see bugzilla) and if
> we fixed a few of those, the reporting systems would work a lot better
> and more reliably. I am struggling to find anyone to work on that right
> now :(. Its just one example of where some help from others would go
> help improve the core of the project for the benefit of all.
I was in contact Andreea about some of these errors.yp.org issues when I
was extending/re-writting it for our purposes and fixing the issues I found
along the way, but we didn't get very far into integrating my fixes.
Since then it was re-written by Michael Wood so I cannot easily upstream
my changes and I'm not very interested in the re-write, because our version
just works.
I'll send patch which shortens too long failure logs, because it helps
reporting errors from bitbake world builds.
Cheers,
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2015-09-02 20:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 17:40 Patch merge process Khem Raj
2015-09-01 20:04 ` Richard Purdie
2015-09-01 23:17 ` Khem Raj
2015-09-02 7:31 ` Richard Purdie
2015-09-02 20:29 ` Martin Jansa [this message]
2015-09-01 21:55 ` Martin Jansa
2015-09-01 22:05 ` Otavio Salvador
2015-09-01 22:46 ` Khem Raj
2015-09-01 22:51 ` Otavio Salvador
2015-09-02 7:09 ` Richard Purdie
2015-09-08 18:18 ` Trevor Woerner
2015-09-08 18:39 ` Khem Raj
2015-09-08 21:06 ` Martin Jansa
2015-09-10 14:05 ` Alexander Kanevskiy
[not found] ` <CANFkWp=w7Lj_M4hPdBjNya+EHd_9oMJ9QM-ewGO2AAsxJs-9uA@mail.gmail.com>
2015-09-10 14:18 ` Martin Jansa
2015-09-10 15:23 ` Alexander Kanevskiy
2015-09-10 15:39 ` Martin Jansa
2015-09-10 16:55 ` Otavio Salvador
2015-09-01 22:45 ` Khem Raj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150902202903.GA29340@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox