From: Steffen Sledz <sledz@dresearch-fe.de>
To: openembedded-devel@lists.openembedded.org
Cc: Paul Menzel <paulepanter@users.sourceforge.net>
Subject: Re: [2011.03-maintenance] do_compile failed for cacao_0.99.3.bb
Date: Wed, 31 Aug 2011 08:59:10 +0200 [thread overview]
Message-ID: <4E5DDBBE.4050007@dresearch-fe.de> (raw)
In-Reply-To: <1314707457.3796.19.camel@mattotaupa>
On 30.08.2011 14:30, Paul Menzel wrote:
> Am Dienstag, den 30.08.2011, 12:51 +0200 schrieb Steffen Sledz:
>> On 25.08.2011 16:09, Steffen Sledz wrote:
>>> On 25.08.2011 12:59, Steffen Sledz wrote:
>>>> On 24.08.2011 17:22, Jesse Gilles wrote:
>>>>> On Tue, 2011-08-23 at 13:16 -0400, George C. Huntington, III wrote:
>>>>>> I suspect that the problem is happening earlier, classpath isn't building.
>>>>>> the javac wrapper eats the return code from a java compile.
>>>>>
>>>>> If George is right, then the following patch to the javac wrapper script
>>>>> may fix the issue. It fixes building classpath as well as returns the
>>>>> error code if all javac attempts fail.
>>>>>
>>>>> http://patches.openembedded.org/patch/9521/
>>>>
>>>> In our case this patch helps.
>>>>
>>>> If nobody has objections i will commit this patch to oe-dev master and request a pull to 2011.03-maintenance.
>>>
>>> It would be still better if we can get some Acks from a java maintainer.
>>
>> No NACKs after another week. So i pushed the patch do oe-dev master.
>
> Next time it would be better to resend the patch with a appropriate
> subject line.
>
> Unfortunately the commit message [1] does not conform to our commit
> policy [2].
>
> Please make sure to check those things next time. I feel uncomfortable
> to ask new contributors to comply every time but when they look at the
> commit history they see that the policies are often not cared about.
Mea culpa. I should have asked the contributor to resend the patch with a policy conforming comment. Sorry.
Do we still have a chance to change the comment if the patch was already pushed?
Steffen
> [1] http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=16a8a1e9175035b55d91a141d5302c38d63c16f1
> [2] http://openembedded.org/index.php/Category:Policy
--
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
next prev parent reply other threads:[~2011-08-31 7:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 12:13 [2011.03-maintenance] do_compile failed for cacao_0.99.3.bb Steffen Sledz
2011-08-19 14:30 ` Steffen Sledz
2011-08-23 7:28 ` Steffen Sledz
2011-08-23 7:35 ` Robert Schuster
2011-08-23 7:49 ` Steffen Sledz
2011-08-23 17:16 ` George C. Huntington, III
2011-08-24 15:22 ` Jesse Gilles
2011-08-24 17:40 ` Tom Rini
2011-08-24 18:25 ` Koen Kooi
2011-08-25 10:59 ` Steffen Sledz
2011-08-25 14:09 ` Steffen Sledz
2011-08-30 10:51 ` Steffen Sledz
2011-08-30 12:30 ` Paul Menzel
2011-08-30 15:25 ` George C. Huntington, III
2011-08-31 6:59 ` Steffen Sledz [this message]
2011-08-31 14:25 ` Jesse Gilles
2011-08-31 6:51 ` Robert Schuster
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=4E5DDBBE.4050007@dresearch-fe.de \
--to=sledz@dresearch-fe.de \
--cc=openembedded-devel@lists.openembedded.org \
--cc=paulepanter@users.sourceforge.net \
/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