You don't loose the history when rebasing ... you sort of serialize it. Ok the
order of commits is messed up, but I never really care about this.
It might look less interesting in a GIT visualization tool where you could see
tons of different branches and merges, but it should be a lot easier to
Have a look at this ... I think it explains things quite well.
https://www.youtube.com/watch?v=cSf8cO0WB4o
Chris
Von: Erik de Bruin
Gesendet: Mittwoch, 2. Juli 2014 10:07
An: dev@flex.apache.org
Betreff: Re: New Flex to JS project
Ok, just checking:
I
No effort at all ... that's what GIT rebase is for.
You can think of this sort of an automated "Create-Patch, Revert, Update, Apply
Patch" ... if all goes well, it's just this one command, if there are
conflicts, you get the usual conflict editor you would get anyway if you
created conflicts on
I think the reason for the overlay is that by this we are tricking the
FlashBuilder to use Falcon instead of the old compiler.
It should be possible to have Falcon separate from the normal compiler. It's
just that FlashBuilder will probably not be albe to use it that way.
Probably IntelliJ would
