From: Andrew Davis <afd@ti.com>
To: Randolph Sapp <rs@ti.com>, <reatmon@ti.com>, <denis@denix.org>,
<detheridge@ti.com>
Cc: <meta-ti@lists.yoctoproject.org>
Subject: Re: [meta-ti][master/kirkstone][PATCH 1/2] ti-img-rouge-umlibs: move to new subdir
Date: Tue, 30 May 2023 11:48:35 -0500 [thread overview]
Message-ID: <5dae44a0-547b-a158-f261-4fceb5882718@ti.com> (raw)
In-Reply-To: <2cbefdef-f4a7-ad47-7533-7296f81d4d24@ti.com>
On 5/30/23 11:38 AM, Randolph Sapp wrote:
> On 5/30/23 10:51, Andrew Davis wrote:
>> On 5/26/23 8:58 PM, Randolph Sapp via lists.yoctoproject.org wrote:
>>> From: Randolph Sapp <rs@ti.com>
>>>
>>> Move recipe to new rogue subdir since we offer more than just libgles
>>> now.
>>>
>>
>> I did something like this as part of: https://lists.yoctoproject.org/g/meta-ti/message/16381
>>
>> ti-img-gpu-umlibs as the name feels more consistent to me.
>>
>> Andrew
>>
>
> Yeah, but even if it is more consistent, the current name matches the git repo on git.ti.com. Unless I'm given explicit permission to rename that I'd prefer those to match as opposed to introducing our own naming convention for everything. We aren't marketing after all :)
>
I mean just for the dir name, that way SGX can go in the same dir.
As for project repo names, yeah I know.. SGX is still named "omap5-sgx-ddk-um-linux",
it doesn't even support OMAP5 anymore :)
Andrew
>>> Signed-off-by: Randolph Sapp <rs@ti.com>
>>> ---
>>> .../{libgles => rogue}/ti-img-rogue-umlibs_23.1.6404501.bb | 0
>>> 1 file changed, 0 insertions(+), 0 deletions(-)
>>> rename meta-ti-bsp/recipes-graphics/{libgles => rogue}/ti-img-rogue-umlibs_23.1.6404501.bb (100%)
>>>
>>> diff --git a/meta-ti-bsp/recipes-graphics/libgles/ti-img-rogue-umlibs_23.1.6404501.bb b/meta-ti-bsp/recipes-graphics/rogue/ti-img-rogue-umlibs_23.1.6404501.bb
>>> similarity index 100%
>>> rename from meta-ti-bsp/recipes-graphics/libgles/ti-img-rogue-umlibs_23.1.6404501.bb
>>> rename to meta-ti-bsp/recipes-graphics/rogue/ti-img-rogue-umlibs_23.1.6404501.bb
>>>
>>>
>>>
>>> -=-=-=-=-=-=-=-=-=-=-=-
>>> Links: You receive all messages sent to this group.
>>> View/Reply Online (#16615): https://lists.yoctoproject.org/g/meta-ti/message/16615
>>> Mute This Topic: https://lists.yoctoproject.org/mt/99161819/3619733
>>> Group Owner: meta-ti+owner@lists.yoctoproject.org
>>> Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub [afd@ti.com]
>>> -=-=-=-=-=-=-=-=-=-=-=-
>>>
>
next prev parent reply other threads:[~2023-05-30 16:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-27 1:58 [meta-ti][master/kirkstone][PATCH 0/2] ti-img-rouge-umlibs: housekeeping and version bump rs
2023-05-27 1:58 ` [meta-ti][master/kirkstone][PATCH 1/2] ti-img-rouge-umlibs: move to new subdir rs
2023-05-30 15:51 ` Andrew Davis
2023-05-30 16:38 ` Randolph Sapp
2023-05-30 16:48 ` Andrew Davis [this message]
2023-05-27 1:58 ` [meta-ti][master/kirkstone][PATCH 2/2] ti-img-rogue-umlibs: bump version and explicitly package rs
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=5dae44a0-547b-a158-f261-4fceb5882718@ti.com \
--to=afd@ti.com \
--cc=denis@denix.org \
--cc=detheridge@ti.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=reatmon@ti.com \
--cc=rs@ti.com \
/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.