[p4] nothing better about PVCS?

Glenn Kasten gkasten at peerless.com
Sat Jan 22 14:15:52 PST 2000


I've used both PVCS Version Manager and Perforce,
and have to agree that Perforce is a lot better overall.

I've found that it hard to explain Perforce's unusual branching style
to people who are used to traditional branching.
I think the Perforce branching is good when you want to branch a whole project,
but is weak when you only want to branch a few randomly-located files (e.g. for
a bug fix or minor
new feature), because it requires a new copy of the directory tree on the
client.
One of our engineers works remotely over a slow connection, and finds
it takes a long time to do the first 'integrate' when starting a branch.

Regarding modification time - I haven't found a way to set
the submission time to the time when the file was last modified.
For example, I've received a bunch of files from an outside supplier
in a tar or ZIP archive. I un-archive them and timestamps are correct,
but when I submit them it sets the timestamp to the current time.
It would be nice to have an option for the add command to do that.

Glenn






More information about the perforce-user mailing list