2010/1/16 Alexander Klenin <[email protected]>: > > One big patch is hard or impossible to review.
Correct, and something I have a real issue with in tiOPF (svn) repository. With Git it is much easier to break such a large feature into smaller chunks with smaller specific "micro" features. With the 'git gui' and 'git commit -i' you can select specific hunks or lines of code which must go into the next commit (and still keep the rest of the changes for later commits) - very different to SVN which pretty much forces a everything or nothing commit. > Look how it is done on LKML or git mailing list Yes, good examples. There workflow and usage of branches and promoting features is very efficient, and makes releases much easier and stable. > No, you can export patches from git in a traditional format, > so pulling from you is not necessary. Correct, and that is how I contribute patches to Lazarus project. For each bug fixes (mine or testing somebody else), or when implementing new features, I create a "feature" branch, that way I can instantly switch to a clean (trunk) branch if I need to. -- Regards, - Graeme - _______________________________________________ fpGUI - a cross-platform Free Pascal GUI toolkit http://opensoft.homeip.net/fpgui/ -- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
