# A Perforce Job Spec Specification. # # Updating this form can be dangerous! # See 'p4 help jobspec' for proper directions. Fields: 101 Job word 32 required 102 Status select 10 required 103 User word 32 once 104 Date date 20 always 106 Type select 10 required 107 ChangeNumber word 10 optional 105 Description text 0 required Comments: # A Perforce Job Specification. # # Job: The job name. 'new' generates a sequenced job number. # Status: Either 'open', 'closed', or 'suspended'. Can be changed. # User: The user who created the job. # Date: The date this specification was last modified. # Type: One of "Addendum","job-ED20M" # ChangeNumber: If an addendum, which change to append to. # Description: Comments about the job/addendum. Required. Values-Status: open/suspended/closed Preset-Status: open Preset-User: $user Preset-Date: $now Values-Type: Addendum/job-ED20M Preset-Type: Addendum Preset-Description: $blank
| # | Change | User | Description | Committed | |
|---|---|---|---|---|---|
| #1 | 345 | paul_goffin |
P4 Append - allows users to append comments to submitted change descriptions. Works by using "jobs" (required modified jobspec included) to communicate the data to the system, then a demon process (actually only tested on NT running as a service) harvests the job data and using "super" rights appends the text from the job to the change and then deletes the job. Only allows the original change author (and members of a specific group) to append to comments. |