Re: Mozilla version control requirements and git

From: Jon Smirl <jonsmirl@gmail.com>
Date: Sep 3, 2006, 03:29 UTC
Message-ID: <9e4733910609022029q9cb9ba9m87cbc37e8d6f4ad7@mail.gmail.com>
In-Reply-To: <46a038f90609021819v6d427f0eh69bc13b30ef6b692@mail.gmail.com>

On 9/2/06, Martin Langhoff <martin.langhoff@gmail.com> wrote:

Show 9 quoted lines

> On 9/3/06, Jon Smirl <jonsmirl@gmail.com> wrote:
> > The Mozilla people have a web page describing what they are looking
> > for in a new version control system. How does git stack up?
>
> Hi Jon,
>
> you've been playing with GIT quite a bit by now, so I guess you know
> the answer ;-) Is there anything in particular you are wondering
> about?

Shallow clones are a big problem. We have Mozilla down to 450MB is git, but that is still gigantic for anyone doing an initial check out, especially if they don't have good broadband. It is over 10x the data that CVS brings down. Even without doing shallow clones git still needs to be modified to restart an interrupted pack transfer.

Show 5 quoted lines

>
> The one item that sticks out for me as not there is ACLs, but access
> controls can be implemented in hooks for direct pushes. Maintain an
> .htaccess-like file and have a perl script to check it on pushes to
> the repo.

I don't see ACLs as that big an issue. If you convert to model where everyone has their own repo and you just push changesets at each other, ACLs are much less important. You need ACLs when 2,000 people have commit privs.

>
> Oh, and "partial tree pulls for localisers". Perhaps git-cvsserver can
> help there? Localisers can just use TortoiseCVS and get a checkout of
> the language pack subdir.

Partial repo pulls and an issue to. The mozilla repo has much more than a browser in it, it also has a large mail/news program. A partial repo pull may not be what is needed for git, instead git needs a partial repo checkout.

-- 
Jon Smirl
jonsmirl@gmail.com

-- 
VGER BF report: U 0.827771