From: Steffen Sledz <sledz@dresearch-fe.de>
To: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: How to verify patches for oe-dev master?
Date: Fri, 09 Sep 2011 12:23:00 +0200 [thread overview]
Message-ID: <4E69E904.6050109@dresearch-fe.de> (raw)
At the moment we're using the 2011.03-maintenance branch with angstrom-2008.1, and we have a problem verifying patches.
Assuming we've found a fix to a bug in 2011.03-maintenance. In my opinion the fix should go to oe-dev master first and find it's way to 2011.03-maintenance by a pull request.
The problem is that oe-master does not support angstrom-2008.1 any more, so it's hard to check if the patch compiles/runs well under oe-master.
Any suggestions?
Steffen
--
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 reply other threads:[~2011-09-09 10:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 10:23 Steffen Sledz [this message]
2011-09-12 14:19 ` How to verify patches for oe-dev master? Steffen Sledz
2011-09-12 14:46 ` Marco Cavallini
2011-09-12 14:52 ` Steffen Sledz
2011-09-12 15:09 ` Marco Cavallini
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=4E69E904.6050109@dresearch-fe.de \
--to=sledz@dresearch-fe.de \
--cc=openembedded-devel@lists.openembedded.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