(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
like the headline "The Easy Way") ;-)
>
>Chris
>
>Von: Alex Harui
>Gesendet: Mittwoch, 3. September 2014 17:04
>An: dev@flex.apache.org; Kessler CTR Mark J
>Betreff: RE: How to manage flex-utilities git repo
>
>Do any g
e-git-repository/17864475#17864475
(I particular like the headline "The Easy Way") ;-)
Chris
Von: Alex Harui
Gesendet: Mittwoch, 3. September 2014 17:04
An: dev@flex.apache.org; Kessler CTR Mark J
Betreff: RE: How to manage flex-utilities git r
y
of the other files as well I presume.
-Mark
-Original Message-
From: Alex Harui [mailto:aha...@adobe.com]
Sent: Tuesday, September 02, 2014 3:17 PM
To: dev@flex.apache.org
Subject: Re: How to manage flex-utilities git repo
Infra responded rather quickly to the flex-radii8 request. It
ember 02, 2014 3:17 PM
To: dev@flex.apache.org
Subject: Re: How to manage flex-utilities git repo
Infra responded rather quickly to the flex-radii8 request. It would be
already created but I didn't tell them if it was supposed to be a bare
repo or an import of another repo.
So, I think we sh
ion as a second best.
>
>
>-Mark
>
>-Original Message-
>From: Alex Harui [mailto:aha...@adobe.com]
>Sent: Tuesday, September 02, 2014 11:57 AM
>To: dev@flex.apache.org
>Subject: Re: How to manage flex-utilities git repo
>
>
>
>On 9/2/14 5:31 AM, "Kessler C
Harui [mailto:aha...@adobe.com]
Sent: Tuesday, September 02, 2014 11:57 AM
To: dev@flex.apache.org
Subject: Re: How to manage flex-utilities git repo
On 9/2/14 5:31 AM, "Kessler CTR Mark J" wrote:
>+1
>
>I like the idea. I can see Justin's concerns too. Is there a way
On 9/2/14 5:31 AM, "Kessler CTR Mark J" wrote:
>+1
>
>I like the idea. I can see Justin's concerns too. Is there a way to
>have multiple github repos one with each of the dev-subprojects ?
I've asked for a new repo for radii8. We'll see how quick it is to get
one. If you look at the total s
'dev@flex.apache.org'
Subject: How to manage flex-utilities git repo
Hi,
while working on Squiggly, FlexPMD and the Mavenizer I too realized that the
way we are currently doing things here is far from ideal as merging stuff back
to master is allmost impossible.
How about not having a "deve
August 2014 07:49
An: dev@flex.apache.org
Betreff: Re: How to manage flex-utilities git repo
OK, so should I ask Infra for flex-radii8 or do we want to try this idea on it?
If I understand, I would create a radii8 branch and check the code in there?
-Alex
On 8/30/14 10:05 PM, "Harbs" wrote:
&
OK, so should I ask Infra for flex-radii8 or do we want to try this idea
on it?
If I understand, I would create a radii8 branch and check the code in
there?
-Alex
On 8/30/14 10:05 PM, "Harbs" wrote:
>I like it.
>
>On Aug 30, 2014, at 6:13 PM, Christofer Dutz
>wrote:
>
>> Hi,
>>
>> while work
Hi,
One (minor) down side is that work will not show up in git hub default ranch
(develop?) until changes are merged into it. This makes the project look less
active than it is.
Justin
I like it.
On Aug 30, 2014, at 6:13 PM, Christofer Dutz wrote:
> Hi,
>
> while working on Squiggly, FlexPMD and the Mavenizer I too realized that the
> way we are currently doing things here is far from ideal as merging stuff
> back to master is allmost impossible.
>
> How about not having a
+1
The first workable sounding solution.
Thanks Chris!
EdB
On Saturday, August 30, 2014, Christofer Dutz
wrote:
> Hi,
>
> while working on Squiggly, FlexPMD and the Mavenizer I too realized that
> the way we are currently doing things here is far from ideal as merging
> stuff back to master
Hi,
while working on Squiggly, FlexPMD and the Mavenizer I too realized that the
way we are currently doing things here is far from ideal as merging stuff back
to master is allmost impossible.
How about not having a "develop" branch, but one for each sub-project. So when
I start working on the
20 matches
Mail list logo
