Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cdt-dev] The great git migration 2011

Dear All,

I've had a quick look at doing a test migration of the org.eclipse.cdt repo using cvs2git:
   https://bugs.eclipse.org/bugs/show_bug.cgi?id=316208
An early example conversion is @
   https://github.com/jamesblackburn/org.eclipse.cdt

Things committers and contributors may be interested in:

1) Name + Email:

When we move to git, your commit email address will need to match your foundation email address or you won't be able to push into the central repository:
   http://wiki.eclipse.org/Git#Committers_new_to_Git

Please check your name + email are correct:
   https://bugs.eclipse.org/bugs/show_bug.cgi?id=316208#c6

2) Repository partitioning:

There seems to be some consensus that a single CDT repository (at least initially) is preferable to a split repo. This makes it easier to clone, perform atomic commits and push with single operations:
 https://bugs.eclipse.org/bugs/show_bug.cgi?id=316211

At a later date we can carve out portions of the repository into separate smaller repositories preserving history.

3) Deleting 'Old' (forever!):

There's old content in the repository which isn't built, tested, nor tagged. Some of this content may have moved to other repositories (e.g. linuxtools / mylyn).  We propose to not include this content in the conversion.  The bundles involved are:
  https://bugs.eclipse.org/bugs/show_bug.cgi?id=316208#c7
Including plugins for:
  Mylyn, cppunit, oprofile, rpm, ffs, android, msw, csharp, pdom

4) Timing:

If we are to migrate to git, it would make sense to do exploratory migrations while the repository is frozen during the release period.  This way we can get the git releng up in parallel while very little activity is happening in CVS HEAD.  We can then move without delay to git at the start of Juno.

Comments / questions / flames all welcome :)

Cheers,
James

Back to the top