| Title | Perforce "p4 fix -c change jobname -s status" does the fix (with status closed) and then complains about incorrect arguments after the command |
| Status | suspended |
| Priority | optional |
| Assigned user | Gareth Rees |
| Product | project |
| Organization | Perforce |
| Description | Perforce "p4 fix -c change jobname -s status" does the fix (with status closed) and then complains about incorrect arguments after the command. |
| Analysis | This was observed in Perforce client P4/NTX86/2000.1/17595 and server P4D/NTX86/2000.1/16895. Here's an example. C:>p4 -p 127.0.0.1:1667 -u joe fix -c 1 sprocket_19 -s open spocket_19 fixed by change 1 Job '-s' unknown - use 'job' to create it. Job 'open' unknown - use 'job' to create it. Perforce should verify the whole command line before executing any of it. It is optional for the P4DTI project that this be fixed. |
| How found | manual_test |
| Evidence | <http://www.ravenbrook.com/project/p4dt...c/2000-10-17/release-0.3.1-test-report/>< http://info.ravenbrook.com/mail/2000/10/18/10-54-52/0.txt>< http://info.ravenbrook.com/mail/2000/10/18/17-16-06/0.txt> |
| Created by | Gareth Rees |
| Created on | 2000-10-18 11:23:07 |
| Last modified by | Gareth Rees |
| Last modified on | 2001-12-10 18:57:27 |
| History | 2000-10-18 GDR Created based on test report for release 0.3.1. 2000-11-07 GDR Suspended following e-mail from Perforce: this is fundamental to the way the Perforce command line parser operates. |