From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [oe][meta-oe][PATCH 2/4] xterm: add latest version of xterm
Date: Wed, 10 Apr 2013 14:43:35 -0500 [thread overview]
Message-ID: <5165C0E7.8030203@windriver.com> (raw)
In-Reply-To: <20130410193611.GF2471@jama>
On 4/10/13 2:36 PM, Martin Jansa wrote:
> On Wed, Apr 10, 2013 at 08:10:11PM +0200, Marco wrote:
>> Il 10/04/2013 18:56, Trevor Woerner ha scritto:
>>> This whole thread has me thoroughly confused. Isn't xterm_277.bb
>>> <http://xterm_277.bb> already part of meta-openembedded?
>>>
>>> $ find . -name "*xterm*" -print
>>> ./meta-openembedded/meta-oe/recipes-graphics/xorg-app/xterm_277.bb
>>> <http://xterm_277.bb>
>>>
>>> And from what I can tell, it was added over a year ago by Koen:
>>>
>>> $ git log meta-oe/recipes-graphics/xorg-app/xterm_277.bb
>>> <http://xterm_277.bb>
>>> commit a38efd953c0bfef80fd6819c8339c1d1e79364b3
>>> Author: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org
>>> <mailto:marcin.juszkiewicz@linaro.org>>
>>> Date: Thu Dec 13 10:35:26 2012 +0000
>>>
>>> xterm: added gnu-configize for AArch64 support
>>> Signed-off-by: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org
>>> <mailto:marcin.juszkiewicz@linaro.org>>
>>> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com
>>> <mailto:Martin.Jansa@gmail.com>>
>>>
>>> commit 253b1d7bc35c5a2a12dd6a7f2f0c034a34bfae18
>>> Author: Koen Kooi <koen@dominion.thruhere.net
>>> <mailto:koen@dominion.thruhere.net>>
>>> Date: Fri Jan 13 09:41:51 2012 +0100
>>>
>>> xterm: update to 277
>>> License checksum changed due to date changes
>>> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net
>>> <mailto:koen@dominion.thruhere.net>>
>>>
>>>
>>
>> Yes, it is copied from meta-openembedded into oe-core
>
> Then you should fix commit message too
>
> * Recipe taken from oe-classic
>
> In all recipes you sent to oe-core.
See: http://openembedded.org/wiki/Commit_Patch_Message_Guidelines
Specifically the Example: Importing fro Elsewhere Unmodified (and modified)
It's a good idea to list where it came from the commit.. that way if the
original location is ever changed, people can track what changes may need to be
merged in.
--Mark
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2013-04-10 20:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 14:21 [oe][meta-oe][PATCH 2/4] xterm: add latest version of xterm Marco Cavallini
2013-04-09 14:26 ` Burton, Ross
2013-04-09 17:46 ` Martin Jansa
2013-04-09 18:01 ` Koen Kooi
2013-04-09 19:06 ` Martin Jansa
2013-04-10 5:44 ` Koen Kooi
2013-04-10 16:56 ` Trevor Woerner
2013-04-10 18:10 ` Marco
2013-04-10 19:36 ` Martin Jansa
2013-04-10 19:43 ` Mark Hatle [this message]
2013-04-11 9:02 ` Marco
2013-04-10 22:44 ` Trevor Woerner
2013-04-10 22:53 ` Denys Dmytriyenko
2013-04-11 9:04 ` Marco
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=5165C0E7.8030203@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.