On 28 Aug 2011, at 23:18, Vadim Goncharov wrote:

Yes. Perforce is 'namespace-based'. You map parts of the repository namespace into your client namespace and work from there. Branches are free for most practical purposes and it's reasonably easy to merge between branches.

The main downside of Perforce is that the server likes to track every client's files and that things get very shaky when you try to interfere with that principle. One of my customers uses Perforce without tracking (or tries to) and it goes horribly wrong in a number of ways (gigantic "p4 have" databases, which don't reflect reality, accidental "p4 sync -k" locking up the server for everyone for hours,...).

I think git is a very reasonable system and it should be possible to map the way we work with FreeBSD into git. As has been mentioned elsethread: things would be a lot easier if we had "official git seeds" to pull from which would make it easy to collaborate and then push things up into SVN. Also, a page of "rules for things not to do with git" would be helpful. It would be a bad idea if committers using git pushed changes into Subversion which made subversion impossible to use (or much harder to use than it currently is).

- Philip