[p4] Implement a "p4 checkout"
tal at zapta.com
Mon Jan 17 10:15:15 PST 2000
So why not to implement in Perforce a mv or rename that will do the
integrate+delete thing ?
Mv and rename are very basic operations in file handling. Why do we need to
write wrappers on each platform we use, write internal documentation for it,
teach other users, etc ?
Isn't it the time to implement it in Perforce itself ?
Anybody from Perforce is willing to answer this ?
> -----Original Message-----
> From: perforce-user-admin at perforce.com
> [mailto:perforce-user-admin at perforce.com]On Behalf Of Dave Lewis
> Sent: Monday, January 17, 2000 9:16 AM
> To: tal at zapta.com
> Cc: perforce-user at perforce.com
> Subject: Re: [p4] Implement a "p4 checkout"
> > From: "Tal Dayan" <tal at zapta.com>
> > Date: Sun, 16 Jan 2000 14:20:55 -0800
> > And on a similar note, any idea why Perforce does not have a simple
> > 'mv' or 'rename' operation ?
> I think that without a good deal more sophistication, mv or rename will
> create a situation where an old configuration cannot be reproduced.
> The current method is to branch to the new name and then delete
> the old one.
> In this way, the old file remains available when a client is synced to
> an old state.
> perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user