23 messages in com.perforce.perforce-userYour 97.3 Input Solicited
FromSent OnAttachments
# Cowham01 Jul 1997 00:53 
Chri...@perforce.com03 Jul 1997 14:20 
# Cowham09 Jul 1997 05:16 
Jeff...@uplanet.com09 Jul 1997 08:16 
Erns...@aut.alcatel.at09 Jul 1997 08:18 
Jeff...@uplanet.com09 Jul 1997 08:29 
Adam...@rien.engr.sgi.com09 Jul 1997 08:59 
Jame...@portal.ca09 Jul 1997 09:24 
Adam...@rien.engr.sgi.com09 Jul 1997 10:00 
Nave...@vinayak.engr.sgi.com09 Jul 1997 10:05 
Chri...@millpond.engr.sgi.com09 Jul 1997 10:13 
Jame...@portal.ca09 Jul 1997 10:53 
John...@non.net09 Jul 1997 10:54 
Gerd...@BITart.com09 Jul 1997 11:09 
John...@non.net09 Jul 1997 11:22 
Wayn...@ichips.intel.com09 Jul 1997 11:47 
Gerd...@BITart.com09 Jul 1997 12:06 
Ames...@cloudscape.com09 Jul 1997 13:40 
Davi...@hyperion.engr.sgi.com09 Jul 1997 14:59 
John...@non.net10 Jul 1997 00:22 
Gerd...@BITart.com10 Jul 1997 11:06 
Gerd...@BITart.com15 Jul 1997 17:17 
Tony...@illustra.com15 Jul 1997 17:53 
Subject:Your 97.3 Input Solicited
From:Ames...@cloudscape.com (Ames@cloudscape.com)
Date:07/09/1997 01:40:43 PM
List:com.perforce.perforce-user

Just ran across these with recent new users ...

1) It would be useful if there was a simple way to create users in perforce.
This would then make sure the licenses got to the right people, avoiding
inadvertent mistakes (like with changing case or switching between your name and
your email id). I can do this today by creating a client with the username and
then deleting it, but I'd rather have a 1-step "create a user" command.

2) Have "p4 get" report at the very end the # of files added, deleted, changed,
and in need of a resolve. The bigger our codebase gets, the more likely people
are not to see those messages flashing across the screen.

- - Ames. ames at cloudscape.com