Re: [Flex-devel] Conversion to Git?

[Aaron S. <aa...@se...>]

Absolutely fantastic! Thank you, Will.

On Sun, Jul 15, 2012 at 5:10 PM, Will Estes <wes...@gm...> wrote:
> All,
>
> I'm making arrangements to get flex into git so that things like this
> can happen way more easily.
>
> The basic plan is this:
>
> * Get a release of flex out so that all the recent bug fixes are in the
>   generally available version of flex.
>
> * Get flex imported into git and cleaned up and buildable with the git
> * workflow/toolchain. (In particular, I want to move the *.[ch] files
>   into an src directory and I want to look at making the test suite more
> sane. But I'll also need the git equivalent of cvs2cl, which the
> current cvs tree relies on to build new ChangeLog files.)
>
> If this were the sort of change that didn't touch flex in all kinds of
> places, it'd be more-or-less easy to do in cvs, but what with all the
> changes that Paul has been working on, once I patched the cvs tree, and
> made additional changes to continue work on flex, it'd be a mess again,
> and branching and remerging in cvs are as Aaron notes, dirty words. Git
> rebase, not so much.
>
> --Will
>
> On Tuesday, 10 July 2012,  2:12 pm -0700, Aaron Stone <aa...@se...> wrote:
>
>> In CVS, forking is a dirty word, because merging is extremely hard. In
>> git, a fork is simply your workspace, ready o be pulled back to
>> mainline. It's a fantastically easier workflow.
>>
>> However your point is valid: if mainline flex is in CVS, patches are
>> its workflow :/
>>
>> On Jul 10, 2012, at 1:53 PM, Paul <pa...@pr...> wrote:
>>
>> > I really would rather not effectively fork flex. I would prefer to do
>> > whatever is necessary to integrate with the mainline.
>> >
>> > Paul
>> >
>> > On 07/10/2012 04:43 PM, ruertar wrote:
>> >> On 07/10/2012 04:33 PM, Peter Martini wrote:
>> >>> Any thoughts on converting to Git?  Sourceforge already has a
>> >>> (empty) git repository for flex, and it's not that difficult to
>> >>> convert the CVS repo to Git while preserving all of the history,
>> >>> branches, and tags.  (I've done it locally already).
>> >>>
>> >> I would like this as well.
>> >>
>> >> ------------------------------------------------------------------------------
>> >> Live Security Virtual Conference
>> >> Exclusive live event will cover all the ways today's security and
>> >> threat landscape has changed and how IT managers can respond. Discussions
>> >> will include endpoint security, mobile security and the latest in malware
>> >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> >> _______________________________________________
>> >> Flex-devel mailing list
>> >> Fle...@li...
>> >> https://lists.sourceforge.net/lists/listinfo/flex-devel
>> >>
>> >>
>> >
>> >
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > Live Security Virtual Conference
>> > Exclusive live event will cover all the ways today's security and
>> > threat landscape has changed and how IT managers can respond. Discussions
>> > will include endpoint security, mobile security and the latest in malware
>> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> > _______________________________________________
>> > Flex-devel mailing list
>> > Fle...@li...
>> > https://lists.sourceforge.net/lists/listinfo/flex-devel
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Flex-devel mailing list
>> Fle...@li...
>> https://lists.sourceforge.net/lists/listinfo/flex-devel
>
> --
> Will Estes (wl...@us...)
> Flex Project Maintainer
> http://flex.sourceforge.net/