...@flex.apache.org
Subject: [2/2] git commit: Merge branch 'FLEX-33349' into develop
Merge branch 'FLEX-33349' into develop
* FLEX-33349:
Fix TypeError #1009 happening in dataProviderRefreshed() of List.as after
refreshing the dataProvider of Combobox.
Project: http://git-wip-us.apache.org
d'origine- From: carlosrov...@apache.org
Sent: Wednesday, March 27, 2013 3:12 AM
To: comm...@flex.apache.org
Subject: [2/2] git commit: Merge branch 'FLEX-33349' into develop
Merge branch 'FLEX-33349' into develop
* FLEX-33349:
Fix TypeError #1009 happening in dataProviderRefreshed
://cwiki.apache.org/confluence/display/FLEX/Good+vs+Bad+Git+usage
-Message d'origine- From: carlosrov...@apache.org
Sent: Wednesday, March 27, 2013 3:12 AM
To: comm...@flex.apache.org
Subject: [2/2] git commit: Merge branch 'FLEX-33349' into develop
Merge branch 'FLEX-33349' into develop
/FLEX/Good+vs+Bad+Git+usage
-Message d'origine- From: carlosrov...@apache.org
Sent: Wednesday, March 27, 2013 3:12 AM
To: comm...@flex.apache.org
Subject: [2/2] git commit: Merge branch 'FLEX-33349' into develop
Merge branch 'FLEX-33349' into develop
* FLEX-33349:
Fix TypeError #1009
/confluence/display/FLEX/Good+vs+Bad+Git+usage
-Message d'origine- From: carlosrov...@apache.org
Sent: Wednesday, March 27, 2013 3:12 AM
To: comm...@flex.apache.org
Subject: [2/2] git commit: Merge branch 'FLEX-33349' into develop
Merge branch 'FLEX-33349' into develop
* FLEX
: carlosrov...@apache.org
Sent: Wednesday, March 27, 2013 3:12 AM
To: comm...@flex.apache.org
Subject: [2/2] git commit: Merge branch 'FLEX-33349' into develop
Merge branch 'FLEX-33349' into develop
* FLEX-33349:
Fix TypeError #1009 happening in dataProviderRefreshed() of List.as after
.
Thanks,
-Fred
-Message d'origine-
From: Carlos Rovira
Sent: Wednesday, March 27, 2013 10:24 AM
To: dev@flex.apache.org
Subject: Re: [2/2] git commit: Merge branch 'FLEX-33349' into develop
Hi Frederic,
in our experience working with GIT we saw that was extremely helpful to
have visual
Subject: Re: [2/2] git commit: Merge branch 'FLEX-33349' into develop
Here's how it would Develop, after merging the branches of Charles and Fred, as
you can see, thereby properly appreciate the content of the two applied
Tickets.
However, Justin's commit b5da14a, is visually hidden under
that will be display well.
-Fred
*From:* Jose Barragan jose.barra...@codeoscopic.com
*Sent:* Wednesday, March 27, 2013 1:26 PM
*To:* dev@flex.apache.org
*Subject:* Re: [2/2] git commit: Merge branch 'FLEX-33349' into develop
Here's how it would Develop, after merging the branches
,
-Fred
-Message d'origine-
From: Carlos Rovira
Sent: Wednesday, March 27, 2013 4:03 PM
To: dev@flex.apache.org
Subject: Re: [2/2] git commit: Merge branch 'FLEX-33349' into develop
IMHO this is hard to see, and even more for people outside or coming some
time later in time, but that's only my
change it (but really, I think everyone will be
happy with it).
Thanks,
-Fred
-Message d'origine-
From: Frédéric THOMAS
Sent: Wednesday, March 27, 2013 5:22 PM
To: dev@flex.apache.org
Subject: Re: [2/2] git commit: Merge branch 'FLEX-33349' into develop
Yeah, for sure, it's your point
change it (but really, I think everyone will be
happy with it).
Thanks,
-Fred
-Message d'origine-
From: Frédéric THOMAS
Sent: Wednesday, March 27, 2013 5:22 PM
To: dev@flex.apache.org
Subject: Re: [2/2] git commit: Merge branch 'FLEX-33349' into develop
Yeah, for sure, it's your
Subject: Re: [2/2] git commit: Merge branch 'FLEX-33349' into develop
Another point Carlos,
this is really a matter of tastes. Each one should be happy with his way
of proceed
What should I do a git wiki with the good practices if at the end everyone
does what he wants, I guess we can try
forced merge.
Thanks,
-Fred
-Message d'origine-
From: Carlos Rovira
Sent: Wednesday, March 27, 2013 4:03 PM
To: dev@flex.apache.org
Subject: Re: [2/2] git commit: Merge branch 'FLEX-33349' into develop
IMHO this is hard to see, and even more for people outside or coming some
time
it (but really, I think everyone will be
happy with it).
Thanks,
-Fred
-Message d'origine-
From: Frédéric THOMAS
Sent: Wednesday, March 27, 2013 5:22 PM
To: dev@flex.apache.org
Subject: Re: [2/2] git commit: Merge branch 'FLEX-33349' into develop
Yeah, for sure, it's your
: Wednesday, March 27, 2013 6:06 PM
To: dev@flex.apache.org
Subject: Re: [2/2] git commit: Merge branch 'FLEX-33349' into develop
That's the point Alex...
Any solve can resolve as a single commit or in a change set, and this
decision, under what criterial it does?
--
Jose Barragan
Chief Software
really
develops, there's no artificial forced merge.
Thanks,
-Fred
-Message d'origine-
From: Carlos Rovira
Sent: Wednesday, March 27, 2013 4:03 PM
To: dev@flex.apache.org
Subject: Re: [2/2] git commit: Merge branch 'FLEX-33349' into develop
IMHO this is hard to see
myCommit'
Thanks,
-Fred
-Message d'origine-
From: Carlos Rovira
Sent: Wednesday, March 27, 2013 6:47 PM
To: dev@flex.apache.org
Subject: Re: [2/2] git commit: Merge branch 'FLEX-33349' into develop
Hi Alex,
as I said this is a matter of taste, but we are using git with huge
projects
@flex.apache.org
Subject: Re: [2/2] git commit: Merge branch 'FLEX-33349' into develop
Hi Alex,
as I said this is a matter of taste, but we are using git with huge
projects for months and when we are merging and generating releases and we
end wanting to easily see *all* branches to quickly see
19 matches
Mail list logo
