6 messages in com.perforce.perforce-userbacking out changes?| From | Sent On | Attachments |
|---|---|---|
| Dave...@vignette.com | 15 Oct 1998 08:56 | |
| Sully | 15 Oct 1998 09:35 | |
| Ping...@mit.edu | 15 Oct 1998 09:42 | |
| Dave...@vignette.com | 15 Oct 1998 13:30 | |
| Fred...@mydata.se | 15 Oct 1998 14:43 | |
| Ping...@mit.edu | 15 Oct 1998 17:26 |
| Subject: | backing out changes? |
|---|---|
| From: | Ping...@mit.edu (Ping...@mit.edu) |
| Date: | 10/15/1998 09:42:10 AM |
| List: | com.perforce.perforce-user |
Dave Lewis <dlewis at vignette.com> wrote:
On a fairly regular basis, people come to me asking if they can remove or back out a change they have submitted. I always tell them they can only fix it with another submit of the files they really want.
I think that would be a bad idea. If the functionality existed, then if my client workarea has foo.c#3, and you obliterate it from the depot, it becomes impossible to reproduce the contents of my workarea. The same problem applies to the real functionality of "p4 obliterate", but since it wipes the entire existence of files, "p4 obliterate" is suitable for use on now-completely-dead parts of the depot. Whereas some of your users seem to want to obliterate a revision of a file which is still in active use.
Unless the user checked in something which is illegal (e.g., a violation of NDA agreements) or otherwise threatens their career (e.g., wiseass comments in source code that go a little too far), your users should learn to deal. People shouldn't be allowed to casually rewrite history books; nor should people be able to casually muck with the history recorded by a revision control system, IMO.
I know if we were desperate, we could probably edit the db files or checkpoint, but that's a major inconvenience (our checkpoint runs at midnight, and users have mentioned how inconvenient it is!)
{chuckle} Well, that's an independent problem. You should schedule your checkpointing based on your users' usage patterns, as opposed to picking some nice obvious time like midnight. I think we'd have a small riot if the depot were shut down every night at midnight. We do automatic builds on a nightly basis, but it syncs to the depot at 5am in the morning, at which time even most late-night owls masquerading as hackers have headed home.
For my own amusement, I graphed our last 1000+ changes against the hour in which they were submitted. For us, midnight is still a pretty busy time.
00: 34 01: 27 02: 18 03: 13 04: 16 05: 2 06: 1 07: 2 08: 10 09: 9 10: 32 11: 67 12: 53 13: 61 14: 95 15: 127 16: 111 17: 116 18: 94 19: 85 20: 57 21: 47 22: 52 23: 46
--- Ping Huang <pshuang at alum.mit.edu>; info: http://web.mit.edu/pshuang/.plan Disclaimer: unless explicitly otherwise stated, my statements represent my personal viewpoints only.