At 03:02 PM 6/18/97 -0700, you wrote:

I sent these to support at perforce.com a while back, but here they are again for this list.

No escape from submit after edit

With p4 submit, you do not have a chance to abort the submit after exiting the editor. The workaround is to not save your changes to the change description file so P4 will notice that the description section has not changed and will not proceed with checkin. This assumes you realize you want to abort before leaving the editor. Another approach would be to have P4 echo the description after you finish editing it and ask "OK to submit? [y]" or something like that. This would apply to all commands that pop you into the editor (user, change, etc.).

Change description in code header

It would be helpful if PERFORCE would automatically append the change description to a History comment section in each file header as it now does the version number.

What's not on depot?

It would be helpful to have a command that showed all files on the client that are not reflected in the depot (that is, files I forgot to do a "p4 add" on). Possibilities might be a query option on add (for example p4 add -i *) or a submit-like list edit (maybe p4 add -l). Another way might be a query that just shows local files which have no corresponding file in the depot, the output of which you can pass to add. For example

p4 local > mylist vi mylist p4 add -f mylist

GUI interface for non-developers

We would like to make PERFORCE the tool of choice for document archiving for non-developers (Sales, Marketing, etc.). Since these groups never work from the command line, it would probably be best if a GUI interface were available.

Merge white-space sensitive

The PERFORCE merge tool appears to be white-space sensitive. Is there some way to turn this off? If not, there should be.

Detection of file type problems

A case occurred recently where a garbage character was introduced into an open file. Though the original file was text, p4 opened reported the file as binary, and p4 submit went ahead and added a new version. It would be preferable if PERFORCE detected and warned about such type mismatches, allowing file types to be changed only by some explicit command.

Augment YOUR & THEIR with file identifier

The your/their terminology with merge is never very clear. It would be helpful if the terms were augmented with the full path name and version number of the respective file, even if this means adding extra <<<<< and >>>>> lines to the merge output or extra lines to resolve prompting.

Backout last submit

A number of developers here would like to see an "unsubmit change" command that would get you back to the edit/add/delete stage. It is understood that if subsequent changes have been made to any of the files in the change that the unsubmit would not work. Perhaps you should call it "p4 doh!". :-)

BobA

__________________________________________________________________________ Bob Andrews WebLogic, Inc. Software Engineering Infrastructure 417 Montgomery Street (415) 659-2627 San Francisco, CA 94104 mailto:boba at weblogic.com http://www.weblogic.com/