clarification on git, central repositories and commit access lists

Simon Hausmann hausmann at
Wed Aug 22 08:50:57 BST 2007

On Wednesday 22 August 2007 09:16:58 Oswald Buddenhagen wrote:
> On Wed, Aug 22, 2007 at 08:45:16AM +0200, Thomas Zander wrote:
> > As an example; in Krita we have this excellent GSoC project for color
> > mixing,
> >
> > the author programs in trunk and thus commits everything there.
> now, that's the fundamental problem. the rest of your argumentation
> falls flat with it.
> with tools like svnmerge branches are actually quite usable and there is
> relatively little difference to your "idealized git-based workflow".

The biggest difference is that with git (or any other SCM that can _actually_ 
merge) multiple people can have their branches and merge with each other and 
after merging "annotate" and the like still work. That is not the case with 
svn and svnmerge.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <>

More information about the kde-core-devel mailing list