From kde-core-devel Fri Jul 13 07:09:05 2007 From: "Boyd Stephen Smith Jr." Date: Fri, 13 Jul 2007 07:09:05 +0000 To: kde-core-devel Subject: Re: KDE development with git Message-Id: <200707130209.10941.bss03 () volumehost ! net> X-MARC-Message: https://marc.info/?l=kde-core-devel&m=118431063127441 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--nextPart2431093.LfupacOBG3" --nextPart2431093.LfupacOBG3 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 13 July 2007, Simon Hausmann wrote about 'Re:= =20 KDE development with git': > On Friday 13 July 2007 01:54:39 Boyd Stephen Smith Jr. wrote: > > 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? No; thanks for the hint. > Besides that the feature you're looking for is present, Well, that was *one* example. I'm glad git has addressed this, but I'm=20 still not sure it's appropriate for KDE. > imports of other=20 > project history in git have shown that in average the size of the entire > history compressed is usually just as big as a single source checkout. That's not my experience on *any* of the numerous trees I've pulled down=20 via git-svn. Now, the compressed history is smaller than I expected in=20 some cases, but it's still quite a bit larger that a flat source checkout. Which, IMO, is *fine*. I'm not concerned with the footprint on my disks --= =20 just the time from between thinking "I'll checkout project X" and being=20 ready to hack on project X is quite long. E.g., I'm been continually=20 pulling down KDE revisions for *weeks* since I issues my git-svn clone=20 command. (I'm not sure if git-svn supports --depth yet.) > I=20 > don't think repository size is an argument with git, provided we get the > project boundaries right (which isn't hard I think). I'd prefer keeping everything together like it is now, and using a VCS that= =20 lets users that want less than everything check out individual directories= =20 or files (like SVN). If things are divided up in the future, it should be made easy to maintain= =20 history when moving a class or application across the boundaries. E.g.=20 from koffice to kde to kdelibs or playground to review to trunk= =20 to (maintainence or historical) branch or a combination of those two=20 moves. =20 =2D-=20 Boyd Stephen Smith Jr. ,=3D ,-_-. =3D.=20 bss03@volumehost.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'=20 http://iguanasuicide.org/ \_/ =20 --nextPart2431093.LfupacOBG3 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (GNU/Linux) iD8DBQBGlyUW55pqL7G1QFkRAgACAJ45ji1DhH0rz+U8ob5XmLl52MxawgCdEX+f qyW6oC5/ZRVQZLeRB6v2ccE= =Y5BT -----END PGP SIGNATURE----- --nextPart2431093.LfupacOBG3--