From kde-core-devel  Fri Jul 13 06:37:14 2007
From: Simon Hausmann <hausmann () kde ! org>
Date: Fri, 13 Jul 2007 06:37:14 +0000
To: kde-core-devel
Subject: Re: KDE development with git
Message-Id: <200707130837.18157.hausmann () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=118430868330276
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart394775436.cOn6xEy4bV"

--nextPart394775436.cOn6xEy4bV
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Friday 13 July 2007 01:54:39 Boyd Stephen Smith Jr. wrote:
> On Wednesday 11 July 2007 08:05:43 am Paolo Capriotti wrote:
> > since a few days, I've been experimenting with git for managing my KDE
> > project (playground/games/kboard) and git-svn to interface back to the
> > KDE svn repository.
>
> Yeah, while I haven't gotten around to KDE hacking yet (I'm still pulling
> down revision history via git-svn), I use git pretty much exclusively at
> work, even though the central repository it SVN.
>
> I am really liking git as a tool for myself personally, but there's a
> number of issues with it that I think would make moving the KDE project
> over to it... something approaching disastrous.  The inability for git to
> pull less than the entire history of the project for the initial checkout
> is a large issue (bazaar has fixed this flaw in their distributed VCS).

Have you see git clone's --depth option that addresses this problem?

(see also git/Documentation/technical/shallow.txt for more details)

Besides that the feature you're looking for is present, imports of other=20
project history in git have shown that in average the size of the entire=20
history compressed is usually just as big as a single source checkout. I=20
don't think repository size is an argument with git, provided we get the=20
project boundaries right (which isn't hard I think).


Simon

--nextPart394775436.cOn6xEy4bV
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)

iD8DBQBGlx2eWXvMThJCpvIRAhA3AJ4sFUD31Qi+2r20VsTjCNqLrP41TgCdHeiE
3L+5EmKMtHmecKPuuz81w0w=
=b1Nl
-----END PGP SIGNATURE-----

--nextPart394775436.cOn6xEy4bV--