On Sat, Oct 25, 2008 at 2:18 PM, Brandon [off-list ref] wrote:
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).
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.
On Sat, Oct 25, 2008 at 6:41 PM, David Symonds [off-list ref] wrote:
On Sat, Oct 25, 2008 at 2:18 PM, Brandon [off-list ref] wrote:
quoted
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).
I think there is an even more fundamental problem with this
feature. Since perforce 'forces' developers the checkout files for
edit, eventually you just ignore these warnings because you don't know
if someone is really checking something out to make a change they are
going to commit, or just need to make a file writable to experiment
with some other feature they're working on etc... This feature would
work much better if it were optional. I don't really care about the
feature per se I would just like to be able to state that Git can
offer everything that perforce can.
I would imagine this would require users pushing their changes to a
branch in the central git repo. Then other users could use git log or
cherry to see what files others are interested in (aka declared they
are going to edit)? Not that this is necessarily a good way to work.
quoted
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.
thanks, I'm pretty sure I'm just imagining reading this somewhere, I
just needed some confirmation.