[vtk-developers] VTK moving to Git

Mark Olesen Mark.Olesen at faurecia.com
Fri Mar 19 11:20:02 EDT 2010

On Fri, 2010-03-19 at 10:55 -0400, Berk Geveci wrote:
> In all likelihood, VTK will be a submodule. At least, later in the Git history.
> This Git repo will be completely incompatible with the existing Git
> repository so there will be no cvshead branch in it. Brad King is
> putting a lot of effort into cleaning VTK and ParaView histories. It
> will be very cool but totally incompatible with existing Git repos.

Less cruft ... good stuff.

Incompatibility with the existing git repos is probably not a major
issue. For the number of changes I have, diffing a local branch against
the last merged cvshead will provide enough for making any changes in a
new repo.

Based on my own experience, I anticipate that the move to git will
accelerate the overall development speed and improve flexibility.

BTW: for all of us miscellaneous users who may wish to make merge
requests, it could be quite convenient to continue with github for
collaborative purposes. Forking an existing project is fairly
lightweight, and the http protocol can be quite useful for people
trapped behind firewalls.


This electronic transmission (and any attachments thereto) is intended solely for the use of the addressee(s). It may contain confidential or legally privileged information. If you are not the intended recipient of this message, you must delete it immediately and notify the sender. Any unauthorized use or disclosure of this message is strictly prohibited. Faurecia does not guarantee the integrity of this transmission and shall therefore never be liable if the message is altered or falsified nor for any virus, interception or damage to your system.

More information about the vtk-developers mailing list