Hi, sorry about that. I accidentally pushed those changes to the
develop branch instead of the vf2js branch. I've immediately reverted
them.
Never mind me, carry on.
EdB
On Sun, May 31, 2015 at 7:41 PM, wrote:
> Repository: flex-falcon
> Updated Branches:
> refs/heads/vf2js [created] 2b06e
That’s perfectly OK, take all the time you need.
EdB
On Mon, Oct 6, 2014 at 10:51 AM, Harbs wrote:
> Okay. I’ll probably have a few more commits to “tables” before I merge it
> though.
>
> On Oct 6, 2014, at 11:48 AM, Erik de Bruin wrote:
>
> > ‘develop’, but you’ll have to merge your curren
Okay. I’ll probably have a few more commits to “tables” before I merge it
though.
On Oct 6, 2014, at 11:48 AM, Erik de Bruin wrote:
> ‘develop’, but you’ll have to merge your current ‘tables’ branch into that,
> first, I guess.
>
> EdB
>
>
>
> On Mon, Oct 6, 2014 at 10:44 AM, Harbs wrote:
‘develop’, but you’ll have to merge your current ‘tables’ branch into that,
first, I guess.
EdB
On Mon, Oct 6, 2014 at 10:44 AM, Harbs wrote:
> In plain English, which branch should I push changes to TLF out to?
>
> On Oct 6, 2014, at 11:42 AM, Erik de Bruin wrote:
>
> > I created and publis
Also, someone will need to merge changes to TLF done after I forked the code.
(Sometime in May I think.) If someone has the time to compile a list of
changes, I’ll cherry pick those and merge.
On Oct 6, 2014, at 11:44 AM, Harbs wrote:
> In plain English, which branch should I push changes to T
In plain English, which branch should I push changes to TLF out to?
On Oct 6, 2014, at 11:42 AM, Erik de Bruin wrote:
> I created and published this branch to give us a clean baseline for TLF,
> working towards the 4.14 release.
>
> This means that ‘develop’ can now be used for active developme
I created and published this branch to give us a clean baseline for TLF,
working towards the 4.14 release.
This means that ‘develop’ can now be used for active development (no need
for the ‘tables’ branch).
EdB
On Mon, Oct 6, 2014 at 10:38 AM, wrote:
> Repository: flex-tlf
> Updated Branches
It's in.
I'm pretty sure the caching problem will be in the installer code so I
think I don't have anything else to go into RC3.
-Alex
On 2/28/14 10:48 PM, "Justin Mclean" wrote:
>Hi,
>
>> I was about to push an installer fix to prevent caching of
>> sdk-installer-config.xml.
>No problem I'll
Hi,
> I was about to push an installer fix to prevent caching of
> sdk-installer-config.xml.
No problem I'll hold off making the next RC - just tell me when you're done.
Thanks,
Justin
Hi Justin,
I was about to push an installer fix to prevent caching of
sdk-installer-config.xml.
-Alex
On 2/28/14 10:37 PM, "jmcl...@apache.org" wrote:
>Repository: flex-sdk
>Updated Tags: refs/tags/apache-flex-sdk-4.12.0RC3 [created] f363a0774
Please ignore this: I'm working on updating the 'release' docs on the
Wiki and needed to make sure that what I wrote actually works ;-)
EdB
On Tue, May 21, 2013 at 10:22 AM, wrote:
> Updated Branches:
> refs/heads/releaseX.Y.Z [created] 4de87659c
--
Ix Multimedia Software
Jan Luykenstr
Hi,
Nice to know what repo this was :-)
> Updated Branches:
> refs/heads/develop [created] 5e461b06f
Justin
This automated email leaves something to be desired in the way of
detail... here it is:
Since the flex-falcon project didn't yet have a 'develop' branch, it
was decided to create one and work from that. I took the local
'master' branch of flex-falcon (which was untouched) and created a
local 'deve
13 matches
Mail list logo
