Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Creating a patch with Git

On 16 Jun 2011, at 21:17, James Blackburn <jamesblackburn@xxxxxxxxx> wrote:

On 16 June 2011 21:05, Schaefer, Doug <Doug.Schaefer@xxxxxxxxxxxxx> wrote:

Speaking of which, I’m very close to waving off the conversion until we get some of these issues address.


I think we should be pragmatic about the migration.  egit is still very young, and they're fixing bugs and adding features at an amazing rate.  Other eclipse projects have migrated to git without too much pain, and while they're not as big as us, there haven't been big upsets.  Also importantly the platform are in the process of migrating too with a similar time scale to us.

CDT is unique in having such a diverse set of committers and an even larger group of downstream distributors/re-packagers.  Moving to git isn't just about our committer workflow, it for the community at large.  IMO the people _least_ affected by this change will be the committers, who already have write access to the blessed eclipse repo.  Everyone else on the other hand, has to struggle with brittle forks of the CVS repo., and spend weeks merging at major releases -- I know as I was there once!  By moving to git we help the downstream CDT community write code on top of CDT and hopefully make it easier for them to stay current and contribute back.

I was hoping to be able to revisit objectiveclipse in a fork that I can keep up to date with regular rebasing against the CDT git repository. That wasn't possible with the CVS branch. 

I think your concerns about egit's performance are still valid and still need fixing. There are also other bugs (like deleted files don't show the change indicator and can't be undone) but the question is whether the advantages overcome the disadvantages?

Alex

Back to the top