From: Siddharth Heroor <heroor@ti.com>
To: Denys Dmytriyenko <denys@ti.com>
Cc: "meta-arago@arago-project.org" <meta-arago@arago-project.org>
Subject: Re: [PATCH oe-layersetup] configs: Update glsdk 6.01.00 to point to GLSDK staging trees
Date: Thu, 27 Jun 2013 08:56:42 +0530 [thread overview]
Message-ID: <51CBB0F2.1040807@ti.com> (raw)
In-Reply-To: <20130626135230.GF27031@edge>
On 6/26/2013 7:22 PM, Denys Dmytriyenko wrote:
> On Wed, Jun 26, 2013 at 09:50:57AM -0400, Denys Dmytriyenko wrote:
>> On Wed, Jun 26, 2013 at 12:56:29PM +0000, Maupin, Chase wrote:
>>>> -----Original Message-----
>>>> From: meta-arago-bounces@arago-project.org [mailto:meta-arago-
>>>> bounces@arago-project.org] On Behalf Of Heroor, Siddharth
>>>> Sent: Wednesday, June 26, 2013 6:06 AM
>>>> To: meta-arago@arago-project.org
>>>> Subject: [meta-arago] [PATCH oe-layersetup] configs: Update glsdk
>>>> 6.01.00 to point to GLSDK staging trees
>>>>
>>>> Signed-off-by: Siddharth Heroor <heroor@ti.com>
>>>> cc: Mrinmayee Hingolikar <mrinmayee@ti.com>
>>>> ---
>>>> configs/glsdk/glsdk-06.01.00-config.txt | 4 ++--
>>>> 1 files changed, 2 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/configs/glsdk/glsdk-06.01.00-config.txt
>>>> b/configs/glsdk/glsdk-06.01.00-config.txt
>>>> index 6159262..a4ada4c 100644
>>>> --- a/configs/glsdk/glsdk-06.01.00-config.txt
>>>> +++ b/configs/glsdk/glsdk-06.01.00-config.txt
>>>> @@ -2,9 +2,9 @@
>>>> # repo name,repo uri,repo branch,repo
>>>> commit[,layers=layer1:layer2...:layern]
>>>>
>>>> bitbake,git://git.openembedded.org/bitbake,master,1.17.0,layers=
>>>> -meta-arago,git://arago-project.org/git/meta-
>>>> arago.git,master,ti2013.04.02,layers=meta-arago-distro:meta-arago-
>>>> extras
>>>> +meta-arago,git://git.ti.com/glsdk/meta-
>>>> arago.git,master,ti2013.04.02,layers=meta-arago-distro:meta-arago-
>>>> extras
>>>
>>> I have some concern if you are already starting to branch to your own tree.
>>> I hope we won't see a large divergence here.
>>>
>>> Also, maybe a nitpick but is there a reason you named your repo meta-arago
>>> and meta-ti on git.ti.com? I worry that this will cause confusion with the
>>> true meta-arago and meta-ti on arago-project.org, particularly since you are
>>> using the same tag name too. Can you rename these like the AMSDK did?
Agreed. I'll rename the trees to follow the AMSDK model. I'll send V2
along today.
>>
>> I would agree here as well - hosting meta-ti and meta-arago clones on
>> git.ti.com is very confusing regardless of the name and sets a bad precedent.
>> I would be happy to give you your own trees on arago-project.org either in the
>> personal area or in the projects area. That is how it is done with other
>> Arago-based SDKs - AMSDK, MCSD, etc.
>
> One little clarification - "your own trees for tagging purposes". As we
> discussed, let's try to avoid forking as much as possible - please keep
> upstreaming your changes.
This time around, we will submit patches to meta-arago and meta-ti ahead
of time. I have no intention of maintaining a fork.
Obviously, we want to learn from the past ;-)
>
>
>>>> meta-openembedded,git://git.openembedded.org/meta-
>>>> openembedded,danny,f00028caf257e386c0f3ae46bd4b3ba53dd0729d,layers
>>>> =toolchain-layer:meta-oe
>>>> -meta-ti,git://arago-project.org/git/meta-
>>>> ti.git,danny,ti2013.04.02,layers=
>>>> +meta-ti,git://git.ti.com/glsdk/meta-
>>>> ti.git,danny,ti2013.04.02,layers=
>>>> meta-linaro,git://git.linaro.org/openembedded/meta-
>>>> linaro.git,danny,d0558fa4304592622423582f8b464e1c22cfe6f1,layers=
>>>> oe-core,git://git.openembedded.org/openembedded-
>>>> core,danny,0785489d558c34cacf5cb349949a15e27084efbf,layers=meta
>>>> OECORELAYERCONF=./sample-files/bblayers.conf.sample
>>>> --
>>>> 1.7.0.4
>>>>
>>>> _______________________________________________
>>>> meta-arago mailing list
>>>> meta-arago@arago-project.org
>>>> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
>>> _______________________________________________
>>> meta-arago mailing list
>>> meta-arago@arago-project.org
>>> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
>> _______________________________________________
>> meta-arago mailing list
>> meta-arago@arago-project.org
>> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
>
prev parent reply other threads:[~2013-06-27 3:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 11:06 [PATCH oe-layersetup] configs: Update glsdk 6.01.00 to point to GLSDK staging trees Siddharth Heroor
2013-06-26 12:56 ` Maupin, Chase
2013-06-26 13:50 ` Denys Dmytriyenko
2013-06-26 13:52 ` Denys Dmytriyenko
2013-06-27 3:26 ` Siddharth Heroor [this message]
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=51CBB0F2.1040807@ti.com \
--to=heroor@ti.com \
--cc=denys@ti.com \
--cc=meta-arago@arago-project.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.