Re: Missing File In Repository

Magnus Svensson writes: 

> Andy Chittenden wrote:
>>> In my environment, I tell my users that the use of the "bk gone"
>>> command
>>> is prohibited and they aren't allowed to use it.
>> 
>> Same here. Even if one of bk's commands outputs a helpful hint to do so. 
>> 
> 
> We have experienced the exact same problem(s). Do anyone know if there
> actually exists a safe way of getting rid of files that's been deleted
> with 'bk rm' and we know we will never want to revive?

That is what "bk gone" is for. It's for permamently removing something from 
revision control. Fundamentally, removing things from revision control is 
not safe. You have to be sure of what you are doing. 

I don't like doing it because it rewrites history, and if you're finding 
yourself using it more than once in a blue moon, there is something wrong 
with your process. Prevention is better than cure; recently I put in 
triggers to ensure that people don't check in files larger than a certain 
size. If someone checks in a small file by mistake I just take the hit and 
remove it with bk rm. It'll still be there but at least the history is safe. 

Maybe one day I'll write a book on how to implement an SCM process with BK:) 

regards 

Brendan