5 messages in com.perforce.perforce-user[p4] Perforce Feature Requests
FromSent OnAttachments
Smith, Jeremy R (CACI)28 Apr 2005 13:32 
Wright, Richard28 Apr 2005 16:00 
Grills, Jeff28 Apr 2005 16:16 
Andreas Axelsson28 Apr 2005 23:50 
Robert Cowham29 Apr 2005 03:54 
Subject:[p4] Perforce Feature Requests
From:Grills, Jeff (jgri@soe.sony.com)
Date:04/28/2005 04:16:24 PM
List:com.perforce.perforce-user

I don't think there's a list. People occasionally post things they want here and say "if you want this too email support and put your name on the list".

I have a script in my public.perforce.com directory (//guest/jeff_grills) called p4unsync.pl that does this sort of thing for you and handles most of the nastier stuff (adds, deletes, etc). I don't think it properly reverts out integrations, though. If you specify "-r", it will leave the files in your client such that you could submit them to revert the changes, otherwise it just removes the changes from your client.

There is also a way in p4win to do something very similar, although it's not obvious. If you select a submitted changelist, and right-click and select Sync..., you'll be given a dialog box that will let you choose to sync the files to the revision previous to that changelist. That can go a long way too.

j

________________________________

From: perf@perforce.com [mailto:perforce-user-bounces at perforce.com] On Behalf Of Smith, Jeremy R (CACI) Sent: Thursday, April 28, 2005 3:33 PM To: perforce-user at perforce.com Subject: [p4] Perforce Feature Requests

Can I ask those who are associated with Perforce if there is any access to the list of requested features, or even a top-ten that can be posted? It's one thing to independently decide that a feature is necessary, it's another thing to add your support to one that would come in handy.

Last night, I really wanted a "p4 undo" which could automatically perform the actions of Identify files changed on a changelist. Sync to version prior to that changelist. Identify any files for which that changelist was not the most recent modification. Do an "edit" or "add" as necessary and prepare the changelist

This couldn't be accomplished weeks later after the files had been edited further, but in the case of the "big oops" it would be really handy. We had a developer delete dozens of archived builds yesterday and it took me significant time to build the changelist properly even though none of them had been touched since his last changelist. Luckily, it was all deletes, so it was fairly easy, but a mixed changelist would be harder.

Thanks, Jer