20 messages in com.perforce.perforce-user[p4] Why does the revision keep rolling?
FromSent OnAttachments
Dan Harmer02 Apr 2002 16:14 
Ken Wilson02 Apr 2002 16:22 
Mike Pagel02 Apr 2002 16:32 
Mich...@diversifiedsoftware.com02 Apr 2002 16:40 
Eric Dew02 Apr 2002 17:02 
Paul Goffin03 Apr 2002 00:17 
Paul Bayless03 Apr 2002 06:54 
Gregg G. Wonderly03 Apr 2002 08:23 
Karl Elvis MacRae03 Apr 2002 10:30 
Dan Harmer03 Apr 2002 10:31 
Karl Elvis MacRae03 Apr 2002 13:46 
Robert Prentice03 Apr 2002 15:19 
ste...@vance.com03 Apr 2002 15:46 
Paul Goffin04 Apr 2002 00:09 
Paul Goffin04 Apr 2002 00:19 
Schipper, Martijn (Contractor)04 Apr 2002 05:30 
ste...@vance.com04 Apr 2002 10:21 
Tyler, Tom04 Apr 2002 10:27 
Gordon Broom04 Apr 2002 13:40 
Jeff A. Bowles04 Apr 2002 14:21 
Subject:[p4] Why does the revision keep rolling?
From:Dan Harmer (dhar@xtendsoft.com)
Date:04/03/2002 10:31:52 AM
List:com.perforce.perforce-user

Thanks for all of the replies regarding the rolling revisions--your input was helpful.

I realized that I could always revert unchanged files, but I was just curious if I could toggle a setting somewhere to not roll the revision on unchanged files... and I can so that's great. This whole situation arised from some of the guys here who check out a whole "folder" of files and only modify one or two before checking all of them back in.

-Dan

-----Original Message----- From: perf@perforce.com [mailto:perforce-user-admin at perforce.com]On Behalf Of Eric Dew Sent: Tuesday, April 02, 2002 6:03 PM To: dharmer at xtendsoft.com Cc: perforce-user at perforce.com Subject: Re: [p4] Why does the revision keep rolling?

Perforce (or any other SCM tool) cannot read your mind. If it's checked out for edit and then checked in, then it's checked in. Who knows whether you had some intention of checking in unmodified files? No SCM tool will second guess your commands.

EDEW

Dan Harmer wrote:

I have a file in my client workspace, I open it for edit using p4 edit (as shown in my screenshot below by sig), I don't modify the file at all, and then I submit the file back to the depot. I don't want Perforce to roll the revision unless the file has changed. In the scenario below, I didn't touch the file between commands, yet the revision still increments by one. How can I stop this action? Your help is appreciated--thanks,

-Dan

--------------------------------------------------------------- C:\Projects\perforce\original>p4 edit //davinci/TestFile30.txt //Davinci/TestFile30.txt#8 - opened for edit

C:\Projects\perforce\original>p4 submit Change 1007 created with 1 open file(s). Submitting change 1007. Locking 1 files ... edit //Davinci/TestFile30.txt#9 Change 1007 submitted.