7 messages in com.perforce.perforce-user98.2 upgrade experience| From | Sent On | Attachments |
|---|---|---|
| Mark...@pml.com | 06 Aug 1998 09:58 | |
| Rich...@netapp.com | 06 Aug 1998 10:15 | |
| Eric...@Adobe.COM | 06 Aug 1998 10:16 | |
| Eric...@Adobe.COM | 06 Aug 1998 10:30 | |
| Davi...@home.chat.net | 06 Aug 1998 11:36 | |
| Robe...@netapp.com | 06 Aug 1998 12:43 | |
| SamF...@channelpoint.com | 10 Aug 1998 08:55 |
| Subject: | 98.2 upgrade experience |
|---|---|
| From: | SamF...@channelpoint.com (SamF...@channelpoint.com) |
| Date: | 08/10/1998 08:55:06 AM |
| List: | com.perforce.perforce-user |
David Jeske <jeske at home.chat.net> writes:
On Thu, Aug 06, 1998 at 10:15:34AM -0700, Richard Geiger wrote:
I'm looking for confirmation that the upgrade to 98.2 is a painless operation. We run 97.3 on Windows NT 4.0.
It was pretty painless for us.
The noticable glitch was that a user can no longer do
p4 client -f -d myclient
to remove a client which *they* own and which has opened files.
Why would they want to do that? If they really didn't have the files open anymore, they can do:
p4 revert //... p4 sync -f
-- David Jeske (N9LCA) + http://www.chat.net/~jeske/ + jeske at chat.net
i've had to do this a few times. one scenario is that a user installs a new NT machine, and uses different drive letters (ugh). but, he had files open on the old client. `p4 revert //...' would want to `fix up' the files it's reverting, which is now impossible. easier to just dump and recreate the client.
it seems like i've solved another problem or two with this, but i can't remember what. i'm glad at least superuser can do it; i hope this failsafe functionality never goes completely away!
- - sam