On Tue, Sep 2, 2014 at 2:35 PM, David Given <d...@cowlark.com> wrote: > > Perforce handles very, very large repositories very well. (Repositories > too large for git.) e.g.: >
One of my clients uses Perforce. Yes, it can handle huge repositories very well. The company has a few projects that benefit both from the ability to handle huge repositories and from the level of management control Perforce's user interface uses. But most of the projects have tiny (2 to 5 SW devs) teams that don't benefit from those controls. > (Perforce is *weird*. You thought git was weird? Go use Perforce.) > Yeah, I've used it. Though the above mentioned client has several in-house plug-ins for Perforce that, while add some capabilities the client finds helpful, they also prevent use of some built-in features (for example, it is necessary to manually maintain each project's manifest of files (I did create a plug-in to partially automate this, but it still some manual intervention))
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
