Hi Tim,
The big hang up in the investigation has been the size of our data package.
If we can find one of these established places that is willing to host a
couple Gb size project, then the source will fall into place quite easily.
That was one potential advantage to code.google.com ... we have already
gotten permission to host our entire scenery database there.
Github wrote us back saying: "Git doesn't work very well with large amounts
of binary assets". They didn't offer further explanation to where the
problems might be? Maybe they were just putting the brakes on and didn't
want to offer to allocate us the large space that we needed? Are there any
real potential issues with large repositories of binary assets with git?
Our data package is the big hurdle we need to clear if we are going to
officially move to another service.
Regards,
Curt.
On Fri, Sep 18, 2009 at 4:08 AM, Tim Moore wrote:
> By way of experimentation, and to move the discussion about source control
> forward, I've put git
> repositories for FlightGear and SimGear up at http://gitorious.org/fg.
> These are somewhat special
> in that they include all the history of the project back to 1997, as
> reconstructed from the
> historical CVS repositories. The git repository for SimGear is 7.7M and for
> FlightGear 22M, roughly
> the same size as their actual source trees.
>
> These are not automatic mirrors of CVS, but are intended for new
> development that will be checked
> into CVS, so they will be reasonably well synchronized with CVS. Each repo
> contains a "cvs"
> branch that is a cvsimport of the head of CVS.
>
> How can you use these?
>
> If you're just curious and/or want to learn more about git, clone them,
> build FlightGear,
> and track new development by pulling from them.
>
> If you're a committer or ought to be one :), you can clone the repositories
> on gitorious.org
> and generate merge requests when you've done something cool. If it's
> suitable I'll merge it
> and the change will make its way to CVS.
>
> If you're a committer and experienced with git, ask me and you can commit
> changes directly.
>
> Enjoy,
> Tim
>
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
--
Curtis Olson: http://baron.flightgear.org/~curt/
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
