Perforce 2006.1 Command Reference | ||
<< Previous Chapter p4 fstat |
Table of Contents Index Perforce on the Web |
Next Chapter >> p4 groups |
To delete a group, use p4 group -d groupname, or call p4 group groupname and remove all the users from the resulting form.
Field Name |
Type |
Description |
---|---|---|
Group: |
Read-only |
The name of the group, as entered on the command line. |
MaxResults: |
Writable |
The maximum number of results that members of this group can access from the server from a single command. The default value is unlimited. See the Usage Notes below for more details. |
MaxScanRows: |
Writable |
The maximum number of rows that members of this group can scan from the server from a single command. The default value is unlimited. See the Usage Notes below for more details. |
Timeout: |
Writable |
The duration (in seconds) of the validity of a session ticket created by p4 login. The default value is 43200 seconds (12 hours). To create a ticket that does not expire, set the Timeout: field to 0. |
Users: |
Writable, |
The Perforce usernames of the group members. Each user name must be typed on its own line, and should be indented. |
Subgroups: |
Writable, |
Names of other Perforce groups. To add all users in a previously defined group to the group you're presently working with, include the group name in the Subgroups: field of the p4 group form. Note that user and group names occupy separate namespaces, and thus, groups and users can have the same names. Every member of any previously defined group you list in the Subgroups: field will be a member of the group you're now defining. |
-d groupname |
Delete group groupname. The members of the group are affected only if their access level or maxresults value changes as a result of the group's deletion. |
-i |
Read the form from standard input without invoking the user's editor. The new group specification replaces the previous one. |
-o |
Write the form to standard output without invoking the user's editor. |
See the Global Options section. |
Command |
Counted Entity |
How Affected Users Can Reduce Command Output |
---|---|---|
changes |
Using p4 changes -m numchanges. |
|
p4 changes files |
file revisions |
Use a more restrictive file pattern on the command line. |
files |
Use a more restrictive file pattern on the command line. |
|
file revisions |
Use a more restrictive file pattern on the command line. |
|
files |
Use a more restrictive file pattern on the command line. |
|
fixes |
The -c changenum or -j jobname flags restricts this command appropriately. |
|
p4 fixes files |
files |
Use a more restrictive file pattern on the command line. |
files |
Use a more restrictive file pattern on the command line. |
|
file revisions |
Use a more restrictive file pattern on the command line. |
|
jobs |
The -e jobquery flag restricts the output to those jobs that meet particular criteria. |
|
p4 jobs files |
file revisions |
Use a more restrictive file pattern on the command line. |
files |
Use a more restrictive file pattern and the -a flag to build the label's file set in pieces. |
|
files |
Use a more restrictive file pattern on the command line. |
|
files, as mapped through client view |
Use a more restrictive file pattern on the command line. |
Perforce 2006.1 Command Reference | ||
<< Previous Chapter p4 fstat |
Table of Contents Index Perforce on the Web |
Next Chapter >> p4 groups |