[p4] Reverting binary files

[Ivey, William]

If space is at a premium, you can (assuming you have a recent
version of Perforce and have admin rights) obliterate the
intermediate revision: p4 obliterate //depot/file#2

A less drastic solution to reduce disk space is to replace the
binary with a small text file under the same name within the
repository. (That's been suggested here in the past.) This
leaves the history intact.

Obviously, both methods require caution. Unless you really need
to watch the disk usage, I'd leave it alone. (I usually edit
the comment, though, with something like "Bad Version!")

-Wm


> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com]On Behalf Of Ismael Arroyo
> Sent: Monday, September 18, 2006 12:55 PM
> To: Stephen Vance
> Cc: perforce-user at perforce.com
> Subject: Re: [p4] Reverting binary files
> 
> 
> Thanks Steve :) 
> 
> -----Original Message-----
> From: Stephen Vance [mailto:steve at vance.com] 
> Sent: Monday, September 18, 2006 19:25
> To: Ismael Arroyo
> Cc: perforce-user at perforce.com
> Subject: Re: [p4] Reverting binary files
> 
> You are doing this the correct way. For binaries, you will 
> have 3 files 
> on the server. The idea in having to do it this way is that 
> regardless 
> of whether it was a mistake, #2 is still part of the history of what 
> happened to the file and may have participated in builds, labels, etc.
> 
> Steve