From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Qt git repository report
Date: Wed, 31 Jan 2007 11:57:38 +0100 [thread overview]
Message-ID: <eppskj$1l4$2@sea.gmane.org> (raw)
In-Reply-To: 200701310912.59102.andyparkins@gmail.com
Andy Parkins wrote:
> It's always nice to read positive reports, so I thought I'd point you all at
> this one.
>
> One of the Qt developers posted a blog entry describing the conversion of the
> Qt repository from perforce to git.
>
> http://qtdeveloper.net/archives/2007/01/30/fun-with-git/
>
> Key facts:
> * 13 years worth of changes
> * 94000 revisions
> * 736774 objects
> * Took 3 hours to convert using git-fast-import and a custom script
> * Repository size: 500MB
> * Checkd out tree size: 330MB
>
> I never cease to be amazed by how good git is at its job.
By the way, do any of you know how large original Perforce repository is?
(And why Trolltech uses Perforce from all proprietary and OSS SCMs?)
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2007-01-31 11:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 9:12 Qt git repository report Andy Parkins
2007-01-31 10:34 ` Chris Lee
2007-01-31 15:42 ` Shawn O. Pearce
2007-01-31 10:57 ` Jakub Narebski [this message]
2007-01-31 15:48 ` Shawn O. Pearce
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='eppskj$1l4$2@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).