Just to throw in my wish list for perforce :-):

Note: it is only because I like perforce and plan on using it so much that I write this:

1) p4 merge3 - an integrated 3way merge tool fully supported by perforce without relying on wish, tcl/tk, etc. Exceptable if it relies on perl/java.

2) p4 rename - do something here. Perhaps... rework how files are stored by filename (add two more tables to the relational database?) so that files are stored under some unique file id (UID). The first table would map UIDs to filenames. The second table would be a directory 'catalogue' table, mapping UID to containing directories (which are also mapped to UIDs). This way, 'p4 rename' would do the correct thing - it could really rename the file/directory without creating an integration/branch event (by changing the UID mapping via a changelist). Integrates are then real integrations, and 'renames' are real renames. A goal would be to not slow down p4...

3) client view specs reworked - so that the first hit from top to bottom wins as opposed to the last hit. This to make client specs parse like clearcase config specs (the last hit algorithm leads to annoying and dangerous situations, etc.).

4) pre/post client triggers (including on 'p4 job'). (release 99.? ???)

5) job change history (and protection)

6) p4 reverse (same as below)

7) p4 filelog -i - this would produce an ordered file history analogous to the clearcase command 'cleartool lsvtree ...'. This could then be integrated into the GUI, so a visual graph of the development of a particular file can be viewed.

Just wanted to add that I have been using perforce for only a couple months, and I am very content with it (and very, very happy with support). Please keep up the very great work!

thanks! - -sandy

Date: Wed, 20 Jan 1999 08:43:44 +0100 From: "Tom Björkholm" <tom.bjorkholm at ebc.ericsson.se> To: Perforce mailing list <perforce-user at perforce.com>, support at
perforce.com CC: Tom.Bjorkholm at ebc.ericsson.se

Hi,

we have been using Perforce for more than a year and we are very happy with it. However there are a few improvements that we would like to have:

1) p4 reverse -c <change_number> An easy way to "undo" a submitted change that was all wrong. Of course, this command would not rewrite the history, it would just automatically create a new change with the opposite changes to the bad change. I.e. it would add deleted files, delete added files, and reverse the changes in edited files. 2) p4 ipgroup We like the "p4 group" and "p4 groups" command. It has made administration of users much easier. But we would like to have the equivalent for for IP addresses. 3) recursive groups It wouold really make life easy if a group could be a member of another group. Then we could have one group for each team. The teams would then be members of projects, and would get the access rights assigned to the project. This applies to both groups and ipgroups (see above).

OK, that is our wish list for the next release of Perforce.

Best Regards,

/Tom