From: Jakub Narebski <jnareb@gmail.com>
To: Brian Herman <brianherman@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: Git and Very Large Codebases
Date: Tue, 20 Apr 2010 02:46:47 -0700 (PDT) [thread overview]
Message-ID: <m3eiiae9t1.fsf@localhost.localdomain> (raw)
In-Reply-To: <h2w4ef15ddc1004200200ocd9df12azf62da7419355ae7c@mail.gmail.com>
Brian Herman <brianherman@gmail.com> writes:
> Can git support codebases on the order of magnitude of Gigabytes?
> For example, a game developer might want to use git as their SCM
> software but their codebases can be in gigabytes in scale.
> If git cannot support this how would one begin to create this support?
Take a look at git-bigfiles project.
--
Jakub Narebski
Poland
ShadeHawk on #git
prev parent reply other threads:[~2010-04-20 9:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <s2x4ef15ddc1004200158s2fc6391byfab91784036ac018@mail.gmail.com>
2010-04-20 9:00 ` Git and Very Large Codebases Brian Herman
2010-04-20 9:43 ` Andreas Ericsson
2010-04-20 9:46 ` Jakub Narebski [this message]
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=m3eiiae9t1.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=brianherman@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).