From kde-core-devel  Wed Aug 22 07:50:57 2007
From: Simon Hausmann <hausmann () kde ! org>
Date: Wed, 22 Aug 2007 07:50:57 +0000
To: kde-core-devel
Subject: Re: clarification on git, central repositories and commit access lists
Message-Id: <200708220950.57523.hausmann () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=118776893006223
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart5381095.MRku2WXF86"

--nextPart5381095.MRku2WXF86
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

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 _actuall=
y_=20
merge) multiple people can have their branches and merge with each other an=
d=20
after merging "annotate" and the like still work. That is not the case with=
=20
svn and svnmerge.


Simon

--nextPart5381095.MRku2WXF86
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBGy+rhWXvMThJCpvIRAsJwAKDtjT5guVtTQcZgfGnRCPe2gKyGpQCg8RuT
FKvx3C7Lj0orwEF8e2MGoso=
=StdZ
-----END PGP SIGNATURE-----

--nextPart5381095.MRku2WXF86--