[p4] Peforce History in source code
andrewd at axonet.com.au
Wed Oct 20 17:38:39 PDT 1999
> From: Rajul Vora <rajul.vora at commerceone.com>
> To: perforce-user at perforce.com
> Subject: RE: [p4] Peforce History in source code
> Date: Tue, 19 Oct 1999 17:35:59 -0700
> I concur with the nay-sayers: No $Log$ and yes to the more important
> bug-fixes and enhancements. Currently my favourites:
> 1. Fix P4Win's set password function so it doesn't set P4PASSWD to
> clear-text password (p4 passwd does the right thing but most of my
> users are
> not command-liners)
> 2. Add a 'p4 protects user|file' command that lists all the
> assigned to the user or all the users and their protections on a given
> filespec. There is no quick way right now to know if user A has write
> to //depot/xyz/... or who has list access to //depot/..., etc. short
> parsing the protect, user and group tables and then duplicating the
> algorithm in our own scripts.
> 2. Add nested groups
> 3. Real "RENAME"
I don't plan to use nested groups and it will slow processing down, so I
vote against it.
Sounds silly? No more so than those "voting against $Log".
I wasn't aware this list was a democracy.
I don't plan to use $Log either, but I'm not criticizing those who do.
If you don't want a new feature, don't use it.
If you do want a new feature implemented, repeat your feature request.
Now can we all get back to more important things?
More information about the perforce-user