From Perforce to Git

From: David Symonds <dsymonds@gmail.com>
Date: Oct 25, 2008, 23:41 UTC
Message-ID: <ee77f5c20810251641l4892ff12n7b30667c6fcc903c@mail.gmail.com>
In-Reply-To: <ee77f5c20810251640q4b40d524n7271a0dfa11ebef8@mail.gmail.com>

On Sat, Oct 25, 2008 at 2:18 PM, Brandon <siamesedream01@gmail.com> wrote:

Show 7 quoted lines

>   I'm trying to make a comprehensive comparison of Perforce and Git
> features. There are two things I currently can't find:
>
> 1) "Who's editing what"
>    It's been documented that git can help developers communicate who
> is editing what at any given time like perforce. (assuming there is a
> central repositry) Has anyone seen an example of scripts to do this?

That's the primary feature of Perforce that kills its scalability once you get past a few hundred developers; it bloats the metadata too much. When you're using Git, there's really little point in using it, since you don't declare what files you are going to be editing, and you can find out other people's changes at merge time at your leisure (not just when *you* want to commit).

Show 5 quoted lines

> 2) Symlinks to checkout partial repository
>   I believe I read symlinks could be used to checkout part of a
> repository. Is this true? any references? I imagine submodules is the
> preferred way of doing this, and "narrow" or "partial" or "sparse"
> checkouts are under development

I don't think so. You could use symlinks to *simulate* a bigger repository that is actually made up of smaller repositories.

Dave.