[cmake-developers] How to develop "bigger" features ? git/gitorious etc.

Brad King brad.king at kitware.com
Fri Apr 9 13:02:28 EDT 2010

Alexander Neundorf wrote:
> now that CMake is using git there are multiple ways how things can be done.

Currently we're using a cvs-like, merge-less, rebase-only workflow.
We've discussed moving to the approach described by "git help workflows"
but have not done it yet.  We're planning to do it soon though.

> E.g. I have almost working support for the IAR compilers here locally, not 
> committed yet.
> How should I proceed with this ?

This is our first non-trivial change since the move to Git.
Perhaps this can be the guinea pig change for the new workflow.

> Should I just commit/push it all at once to the git master ?
> Or, should I do the development on a clone e.g. on gitorious and then request 
> a merge ?

Please construct a series of small, logically distinct commits
to give each change its own meaningful commit message.  Each
commit should still be a working CMake that is a step closer
to the final result.  Then publish it on gitorious and we'll
take a look.


More information about the cmake-developers mailing list