Hi,

First of all, let me apologize for missing the Friday's #oooscm meeting, 
should not happen any more.

On Thursday 29 November 2007 17:41, Jens-Heiner Rechtien wrote:

> John, Jan were you able to 
> do imports with a comparable history as the subversion repository on
> o3-build? I would gladly place them on o3-build for some real comparisions.

I've just pinged Heiner on IRC that I have a git import comparable to the SVN 
one & started uploading it to the server.  He will then move it to a good 
place ;-)

I created it using a patched git-svnimport & _unpatched_ cvsps (so for 
INTEGRATION commits, you usually get lots of them, one per file - but I think 
it is the same what you get with cvs2svn, so it is probably fair.  But for 
the _real_ import, this should be addressed - it's painful to see the 
LGPL+SISSL->SISSL change producing tens of thousands of commits.)  The 
git-cvsimport patches are here:
http://svn.gnome.org/viewvc/ooo-build/trunk/git/git-cvsimport-ooo.diff
http://svn.gnome.org/viewvc/ooo-build/trunk/git/git-cvsimport-upstream.diff

It took 38hrs, 40min on a really fast machine with 8G RAM and not that fast 
disks, so it could be even faster on a machine with a beautiful disk array 
and even more memory ;-)  The import has 2.6G, and contains the commits 
according to Heiner's list until 2007-09-24.  The version of git was 1.5.3.4.

> I've played around a bit with the bazaar branch vs. checkout resp.
> checkout --lightweight feature. I do very much like that it is possible
> with bazaar to mix freely between centralized repositories for our small
> teams and full local repositories for our nomadic developers. Best of
> both worlds here. Is there a similar functionality in git?

Yes, git has so called 'shallow clone'.  Unfortunately I did not test it too 
well yet to be able to tell you the exact way to use it - will do in the 
following days.  For more info, see man git-clone, the option --depth.

Regards,
Jan

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to