[p4] Revision limiting

[Weintraub, David]

Actually, there is another ClearCase feature that would be handy in this
situation. The default behavior of ClearCase's "obliterate" command is
not to remove versions that had labels because those revisions might be
"important". Otherwise, why would you label them?

Something like that on the "p4 obliterate" command would make people
feel better about obliterating older versions since you know that you
won't be destroying anything important.

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Russell C.
Jackson
Sent: Thursday, September 28, 2006 11:27 AM
To: Robert Cowham
Cc: perforce-user at perforce.com
Subject: Re: [p4] Revision limiting

If you don't need the old versions, it is pretty easy to create a script
that will obliterate all the last X revisions. I did this for a team
that said they only needed to keep the last 5 revisions of the binaries
they were checking in available. It has been requested many times that
Perforce support this behavior directly, but so far, they have not
implemented it.

Thanks,
Rusty

--------------------------------------------------
RCJackson Consulting
Perforce Consulting Partner and Certified Trainer
--------------------------------------------------
rusty at rcjacksonconsulting.com
http://www.rcjacksonconsulting.com
tel:      479-696-9710
fax:      479-967-0963
mobile:   479-747-3845
--------------------------------------------------




Robert Cowham wrote:
> Look at Richard Baum's presentation:
>
> http://www.perforce.com/perforce/conf2005/index.html
>
> Note that ICManage do something similar for their customised version 
> of Perforce.
>
> Regards
> Robert
>
>   
>> -----Original Message-----
>> From: perforce-user-bounces at perforce.com
>> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Jeff 
>> Desharnais
>> Sent: 27 September 2006 22:50
>> To: perforce-user at perforce.com
>> Subject: [p4] Revision limiting
>>
>> Hello,
>>
>> We are experiencing an issue where we have large files
>> (250mb) with 150 revisions. My concern is the amount of space this is

>> taking up, and it is starting to cause backup problems (time and 
>> space).
>>
>> My question is in regards to the idea of limiting the amount of 
>> revisions a certain file will retain.
>>
>> If a 250mb file only needs a month of revisions at a time, we could 
>> save many gigs of space. Perhaps store the old revisions on one tape 
>> and leave it locked away.
>>
>> Is there a good (and safe) practice for doing this that anyone could 
>> suggest?
>>
>> Thanks,
>>
>> ---------------------
>> Jeff Desharnais
>> IT Specialist
>> Mad Doc Software
>> 100 Burtt Rd., Suite 220
>> Andover, MA  01810
>> (978) 409-6272 Ext. 132
>>
>> _______________________________________________
>> perforce-user mailing list  -  perforce-user at perforce.com 
>> http://maillist.perforce.com/mailman/listinfo/perforce-user
>>
>>
>>     
>
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com 
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>
>
>   
_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user