I would think a "p4reedit" script could be written that does "p4 describe" for your changelist, extracts the filenames, and feeds them into a "p4 -x - edit" command. You would run "p4reedit" after your p4 submit.

Viktor Haag <vhaag at rim.net> on 2000-01-24 14:47:47

As a write, I work in a fundamentally different manner from developers. Is there a way in Perforce to submit a set of changes to a repository, but still maintain a file open for editing? (i.e., in RCS, this would be ci -l)? It seems kind of silly for me to checkout a dozen chapter files for editing, make changes to them, and then submit those changes, and check them all out again, when I'm the only one really working on the book (although I check in the changes, so that other people can see those changes by syncing their own work areas, those other people (the developers) won't be editing the files, only looking at them).