> I think Matthew and Dave caught the gotchas, so I'm just going to second
> the motion to use delete instead of obliterate. I've used obliterate
> once, two days ago, when I added a new vendor drop to the depot and
> realized I put it in the wrong place. No use having history which wasn't
> meant to be. All other should be kept, IMHO.
Just a couple more comments...
I believe in nearly 100% of our oblits, we are removing stuff that
people just checked in to the wrong place. Like somebody checked in
a thirdparty tree, but it went into the wrong area, so we oblit that
and re-do the initial checkin correctly.
There have also been a few "case sensitive" oblits, where somebody
has created an alternate directory with the wrong case.
I might also, sometime in the future "split" our depot in two by
creating a duplicate depot and then obliterating very old
dead projects from one, and the new current projects from the other.
I haven't really thought about that much, however.
As far as the depot being locked during the oblit, I believe
perforce has greatly improved the db locking in recent releases.
In our last oblit, it took appx 10 minutes to eliminate a
thirdparty mess! Our db.* files are about 12gig.
We currently have some stuff scheduled for oblit, and I'm going to
try to see what the extent of "lockup" is. Several years ago,
nothing would happen during oblits, but currently people can
still sync, and I suspect that now it *might* be possible to even
checkin something... but I'll have to try that!
As I mentioned, we "schedule" stuff for oblit, and this is done
by adding the depots paths to oblit to our "perforce-obliterate"
client. Every few months we then just oblit whatever is in that
client. This keeps us from having to remember exactly what
xxx requested 3 months ago.
OK, I guess that was more than a couple of comments! ;-)
dave
_______________________________________________
Come to the 2005 Perforce User Conference, April 14 & 15 in Las Vegas.
Learn more: http://www.perforce.com/conf
perforce-user mailing list - perforce-user@xxxxxxxxxxxx
http://maillist.perforce.com/mailman/listinfo/perforce-user
|
