(Sorry for the long delay in responding)
On Tue, Nov 4, 2014 at 12:25 PM, Alex Harui wrote:
>
>
> On 11/4/14, 7:52 AM, "OmPrakash Muppirala" wrote:
>
> >
> >We agreed a while ago to move TDF to the flex-examples repo. I still
> >think
> >that is the best place for TDF.
>
> There’s other stuff
On 11/4/14, 7:52 AM, "OmPrakash Muppirala" wrote:
>
>We agreed a while ago to move TDF to the flex-examples repo. I still
>think
>that is the best place for TDF.
There’s other stuff in flex-examples besides TDF Mobile. I think the
whole goal of splitting Git repos is to get one repo per rele
I like this set up as well.
Neil
-Original Message-
From: Kessler CTR Mark J [mailto:mark.kessler@usmc.mil]
Sent: November-04-14 6:24 AM
To: dev@flex.apache.org
Subject: RE: AW: How to manage flex-utilities git repo
It looks good. I thinking it's the right logic for separ
Sent: Monday, November 03, 2014 3:22 PM
> To: dev@flex.apache.org
> Subject: Re: AW: How to manage flex-utilities git repo
>
> Infra wrote back. They want us to dictate a repo set and they’ll try to
> make it happen.
>
> Here’s the proposal:
>
> I would argue that we s
It looks good. I thinking it's the right logic for separating out the pieces
we want independently releasable.
-Mark
-Original Message-
From: Alex Harui [mailto:aha...@adobe.com]
Sent: Monday, November 03, 2014 3:22 PM
To: dev@flex.apache.org
Subject: Re: AW: How to manage
Infra wrote back. They want us to dictate a repo set and they’ll try to
make it happen.
Here’s the proposal:
I would argue that we should leave the following in flex-utilities. I
guess it sort of means that flex-utilities is for code that we don't have
release plans for, but help us do other th
Thanks Chris.
I opened https://issues.apache.org/jira/browse/INFRA-8302 to track a query
into what Infra can or can't do in this regard.
-Alex
On 9/3/14 8:16 AM, "Christofer Dutz" wrote:
>Have to admit that I don't know how to extract parts of a repo.
>
>But a quick google got me to this:
>htt
Have to admit that I don't know how to extract parts of a repo.
But a quick google got me to this:
http://stackoverflow.com/questions/359424/detach-subdirectory-into-separate-git-repository
Which references this one:
http://stackoverflow.com/questions/359424/detach-subdirectory-into-separate-git-r
If we decide to go down this path, we should sort of have a standard fort he
main subproject branch.
I would suggest "develop-{subproject-name}".
This way all develop branches should be sorted and visible together and you
don't have to check if it's just a feature branch of something else.
Is
