From kde-core-devel  Fri Jul 13 17:21:59 2007
From: "Boyd Stephen Smith Jr." <bss03 () volumehost ! net>
Date: Fri, 13 Jul 2007 17:21:59 +0000
To: kde-core-devel
Subject: Re: KDE development with git
Message-Id: <200707131222.03743.bss03 () volumehost ! net>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=118434742809513
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart1733131.zDJaAOjNiU"

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

On Friday 13 July 2007, Simon Hausmann <hausmann@kde.org> wrote about 'Re:=
=20
KDE development with git':
> On Friday 13 July 2007 09:09:05 Boyd Stephen Smith Jr. wrote:
> > > imports of other
> > > 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 via git-svn.  Now, the compressed history is smaller than I
> > expected in some cases, but it's still quite a bit larger that a flat
> > source checkout.
>
> Are you sure your repository is compressed?

With git-repack -a -d, yes?

> Yes, you can start history in git-svn from any revision on. I usually
> start at the top like this:

Well, I actually knew about the -r... I just wasn't thinking about it.

I noticed that the --depth option, results in (pre man git-clone):
"A shallow repository has number of limitations (you cannot clone or fetch=
=20
from it, nor push from nor into it)"

That's a killer for me.  I use multiple computers and definitely need to be=
=20
able to clone / fetch from my "private" repositories.

Does -r have similar limitations?

Is there any way to "back fill" the history that's lost by either of these=
=20
options?  It would be ideal for me if I could grab the last committed tree=
=20
and start hacking while a background process retrieved the rest of the=20
history.  It would also be nice if clone, fetch, etc. would work *if*=20
there was enough history, but error out and/or aggressively fetch the=20
history needed to work.

> Git makes it very easy to migrate history between repositories with
> tools like git filter-branch for example.

'k, I've never had to move code between git repositories, yet.

=2D-=20
Boyd Stephen Smith Jr.                     ,=3D ,-_-. =3D.=20
bss03@volumehost.net                      ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy           `-'(. .)`-'=20
http://iguanasuicide.org/                      \_/    =20

--nextPart1733131.zDJaAOjNiU
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)

iD8DBQBGl7S755pqL7G1QFkRAsagAKCBMP+eMLvVny6dn9UwTWj50HuUggCgjv/Y
De36JWGhFmBWow0FsiqwSR8=
=F9Ia
-----END PGP SIGNATURE-----

--nextPart1733131.zDJaAOjNiU--