AW: [p4] a smart p4 submit - Stephen Vance - com.perforce.perforce-user

10 messages in com.perforce.perforce-userAW: [p4] a smart p4 submit

From	Sent On	Attachments
Rajesh Vaidheeswarran	13 Aug 2001 11:32
wiv...@us.itmasters.com	13 Aug 2001 12:12
Stephen Vance	13 Aug 2001 13:33
Karl Philipp	13 Aug 2001 23:55
Stephen Vance	14 Aug 2001 07:35
Stephen Vance	14 Aug 2001 07:37
Dave Lewis	17 Oct 2001 10:38
Kendall Bennett	17 Oct 2001 11:06
Robert Cowham	17 Oct 2001 11:28
Dave Foglesong	17 Oct 2001 12:08

Subject:	AW: [p4] a smart p4 submit
From:	Stephen Vance (ste...@vance.com)
Date:	08/14/2001 07:35:55 AM
List:	com.perforce.perforce-user

That works because P4Win is a wrapper around the raw Perforce calls. Unfortunately, it still relies on conscious effort, and therefore human fallability, on the part of the developer.

One approach to the wrapper issue is to wrap the p4 command itself. You rename the real command, then create a wrapper called p4. For sub-commands that you want to modify in a way like we are discussing, you can easily have pre- and post- actions. Others you just pass straight through. Doing it in Perl or Python makes it portable.

Steve

At 08:55 AM 8/14/2001 +0200, Karl Philipp wrote:

Hi,

Guessing at Rajesh's intent, he probably wants it happen utomatically on submit. The only way I know of to do that is to wrap the command.

There is a check button called

"Automatically deselect unchanged files before changelist submission"

if you open the Perforce Options dialogbox of P4Win Release 2001.1 and choose the sheet "Miscellaneous".

Unfortunately there is no corresponding item for the command line interface, IMHO.

so long

Karl

Danet GmbH, Business Unit BI Gutenbergstr. 10 64331 Weiterstadt, Germany WWW : http://www.danet.de