From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Figured out how to get Mozilla into git
Date: Fri, 09 Jun 2006 22:44:48 +0200 [thread overview]
Message-ID: <e6cmjn$no5$1@sea.gmane.org> (raw)
In-Reply-To: 9e4733910606091317p26d66579mdf93db293f93fb50@mail.gmail.com
Jon Smirl wrote:
> Martin has also brought up the problem with needing a partial clone so
> that everyone doesn't have to bring down the entire repository. A
> trunk checkout is 340MB and Martin's git tree is 2GB (mine 2.7GB). A
> kernel tree is only 680M.
Partial/shallow nor lazy clone we don't have (although there might be some
shallow clone partial solutions in topic branches and/or patches flying
around in git mailing list). Yet.
But you can do what was done for Linux kernel: split repository into current
and historical, and you can join them (join the history) if needed using
grafts. And even if one need historical repository, it is neede to
clone/copy only _once_. With alternatives (using historical repository as
one of alternatives for current repository) someone who has both
repositories does need only a little more space, I think, than if one used
single repository.
--
Jakub Narebski
Warsaw, Poland
next prev parent reply other threads:[~2006-06-09 20:45 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 2:17 Figured out how to get Mozilla into git Jon Smirl
2006-06-09 2:56 ` Nicolas Pitre
2006-06-09 3:06 ` Martin Langhoff
2006-06-09 3:28 ` Jon Smirl
2006-06-09 7:17 ` Jakub Narebski
2006-06-09 15:01 ` Linus Torvalds
2006-06-09 16:11 ` Nicolas Pitre
2006-06-09 16:30 ` Linus Torvalds
2006-06-09 17:38 ` Nicolas Pitre
2006-06-09 17:49 ` Linus Torvalds
2006-06-09 17:10 ` Jakub Narebski
2006-06-09 18:13 ` Jon Smirl
2006-06-09 19:00 ` Linus Torvalds
2006-06-09 20:17 ` Jon Smirl
2006-06-09 20:40 ` Linus Torvalds
2006-06-09 20:56 ` Jon Smirl
2006-06-09 21:57 ` Linus Torvalds
2006-06-09 22:17 ` Linus Torvalds
2006-06-09 23:16 ` Greg KH
2006-06-09 23:37 ` Martin Langhoff
2006-06-09 23:43 ` Linus Torvalds
2006-06-10 0:00 ` Jon Smirl
2006-06-10 0:11 ` Linus Torvalds
2006-06-10 0:16 ` Jon Smirl
2006-06-10 0:45 ` Jon Smirl
2006-06-09 20:44 ` Jakub Narebski [this message]
2006-06-09 21:05 ` Nicolas Pitre
2006-06-09 21:46 ` Jon Smirl
2006-06-10 1:23 ` Martin Langhoff
2006-06-10 1:14 ` Martin Langhoff
2006-06-10 1:33 ` Linus Torvalds
2006-06-10 1:43 ` Linus Torvalds
2006-06-10 1:48 ` Jon Smirl
2006-06-10 1:59 ` Linus Torvalds
2006-06-10 2:21 ` Jon Smirl
2006-06-10 2:34 ` Carl Worth
2006-06-10 3:08 ` Linus Torvalds
2006-06-10 8:21 ` Jakub Narebski
2006-06-10 9:00 ` Junio C Hamano
2006-06-10 8:36 ` Rogan Dawes
2006-06-10 9:08 ` Junio C Hamano
2006-06-10 14:47 ` Rogan Dawes
2006-06-10 14:58 ` Jakub Narebski
2006-06-10 15:14 ` Nicolas Pitre
2006-06-10 17:53 ` Linus Torvalds
2006-06-10 18:02 ` Jon Smirl
2006-06-10 18:36 ` Rogan Dawes
2006-06-10 3:01 ` Linus Torvalds
2006-06-10 2:30 ` Jon Smirl
2006-06-10 3:41 ` Martin Langhoff
2006-06-10 3:55 ` Junio C Hamano
2006-06-10 4:02 ` Linus Torvalds
2006-06-10 4:11 ` Linus Torvalds
2006-06-10 6:02 ` Jon Smirl
2006-06-10 6:15 ` Junio C Hamano
2006-06-10 15:44 ` Jon Smirl
2006-06-10 16:15 ` Timo Hirvonen
2006-06-10 18:37 ` Petr Baudis
2006-06-10 18:55 ` Lars Johannsen
2006-06-11 22:00 ` Nicolas Pitre
2006-06-18 19:26 ` Linus Torvalds
2006-06-18 21:40 ` Martin Langhoff
2006-06-18 22:36 ` Linus Torvalds
2006-06-18 22:51 ` Broken PPC sha1.. (Re: Figured out how to get Mozilla into git) Linus Torvalds
2006-06-18 23:25 ` [PATCH] Fix PPC SHA1 routine for large input buffers Paul Mackerras
2006-06-19 5:02 ` Linus Torvalds
2006-06-09 3:12 ` Figured out how to get Mozilla into git Pavel Roskin
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='e6cmjn$no5$1@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).