|
|
This topic discusses a problem with the current Vcs OpenAPI that prevents certain operations to be done after a rename or move refactoring. Since the Open API hides any movement of files until check in, there is no way to execute custom VCS actions (checkout, diff, properties, version tree,...) on moved/renamed files. These files simply do not exist for the underlying VCS until check in.
The fact that it is not possible to check out a file after it has been moved/renamed is a very big problem for VCS that relies on explicit writability control: ClearCase, CVS w/ watches, Perforce, VSS. IMHO it is a major flaw in the current implementation. Rename and move actions have to be known/done immediately by the underlying VCS.
big tits
This will break the whole idea of VCS - you perform changes and they are immediately reflected in VCS.
-- MikeAizatsky - 26 Nov 2002
Please feel free to correct any incorrect information or add other VCS in the following table.
The table defines what VCS entry points need to be called at what time and hopefully it will help better understand the required API
big tits al-ama al-ana al-asi al-bbw al-bds al-blo al-boo al-ebo al-foo al-gro al-gy al-han al-har al-int al-lat al-les al-mat al-mil al-pan al-par al-pis al-shm al-tee al-voy ce-ama ce-ana ce-asi ce-bbw ce-bds ce-blo ce-boo ce-ebo ce-gy ce-har ce-int ce-lat ce-les ce-mat ce-mil ce-pan ce-pis ce-shm ce-tee ce-voy vi-ama vi-ana vi-ani vi-asi vi-bbw vi-bds vi-blo vi-boo vi-ebo vi-foo vi-gro vi-gy vi-han vi-har vi-inc vi-int vi-lat vi-les vi-mat vi-mil vi-pan vi-par vi-pis vi-shm vi-tee vi-uni vi-voy
Rename
Move
Create directory (package)
Delete directory (package)
(1) if the content of the file has changed a separate checkinFile would be issued (2) if multiple files were added/deleted/moved/renamed in one directory the checkin of that directory would occur only once -- JacquesMorel - 08 Aug 2002 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||
|
