9 messages in com.perforce.perforce-userRecommended way to rollback a file
FromSent OnAttachments
PatH...@marketguide.com28 May 1999 07:26 
PGof...@baltimore.comPGoffin28 May 1999 07:27 
Jame...@perforce.com28 May 1999 07:50 
PatH...@marketguide.com28 May 1999 08:59 
Jame...@perforce.com28 May 1999 09:04 
PatH...@marketguide.com28 May 1999 09:55 
Scot...@seaslug.org28 May 1999 10:01 
PatH...@marketguide.com28 May 1999 12:10 
Scot...@seaslug.org28 May 1999 16:06 
Subject:Recommended way to rollback a file
From:Scot...@seaslug.org (Scot@seaslug.org)
Date:05/28/1999 04:06:43 PM
List:com.perforce.perforce-user

"Pat Hardy" <phardy at marketguide.com> wrote:

On Fri, May 28, 1999 at 09:04:36AM -0700, James Strickland wrote:

Alternatively: p4 sync file.java#223 p4 edit file.java (gives warning about having to resolve) p4 sync file.java (schedule resolve against head revision) p4 resolve -ay (accept your version)

Which presumably leaves a trace in the 'p4 filelog' of exactly which revision got resurrected (as opposed to my 'p4 print -q' method which would not).

Yes. This is what I need. I want a trace of all changes, even ones that were backed out.

As with all such things...verify before relying on that fact...I don't know for sure if that would leave a trace of which revision it came from or not.

Scott.Blachowicz at seaslug.org