[p4] Client for many users
yariv at Globecom-Interactive.com
Tue Oct 23 00:02:57 PDT 2001
The trivial solution is to create another clients on this machine, one per
If you must work with just one common login, you have another options:
1. Create a client per person, all owned by the common login.
common_user at gilad
common_user at yiftah
common_user at bat_yiftach
(do not forget to locate the workspaces in different directories, to
2. Attach a job to every changelist. In the jobspec, create a field with
that should be filled
with the real user name.
To verify that the job-attachment will be done, you can create a
pre-submit trigger that check if the user name field
From: Gilad Benjamini [mailto:gilad at wanwall.com]
Sent: Tuesday, October 23, 2001 8:21 AM
To: perforce-user at perforce.com
Subject: [p4] Client for many users
In our lab we have a machine which may be used by different developers.
The machine should hold only one source tree, hence, one Perforce client,
owned by one Perforce user.
The machine is mostly for testing, but from time to time code is changed
and submitted on that machine.
How can I make the submitted changes belong to a specific user ?
I tried, while submitting, to change the user's name in the changelist spec,
but Perforce does not allow that.
Any other solution ?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the perforce-user