Jeff Bowles wrote:
I would just 'p4 delete' it. You've got the history in perforce
anyway, so you don't loose anything.''
You might consider, instead, removing permissions on the
codeline.
That way, there's not a 'delete' revision sitting in the child
codeline, expecting to be eventually pushed to the parent lines.
If you're afraid that somebody might 'accidentally' integrate the
deletes into the parent line, I guess a 'null-integration' using 'p4
resolve -ay' could defuse that bomb right away, by marking the delete
changelist as 'already integrated'.
But I concede, there is more than one way to do it.
/Lars
8 messages in com.perforce.perforce-user[p4] What to do with development code...