Summary: | removing file from cvs is not completed by a commit | ||
---|---|---|---|
Product: | [Developer tools] kdevplatform | Reporter: | Martin Köbele <martin> |
Component: | cvs | Assignee: | KDevelop Developers <kdevelop-devel> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | wishlist | ||
Priority: | LO | ||
Version: | 0.9.94 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Martin Köbele
2003-12-09 00:49:08 UTC
This is probably intentional behavior... Amilcar is right: adding files request an explicit user's commit command. Should it be considered a wish? That's anyway the way cvs command line client works ... we may add a checkbox in the user interface but this would require a new cvs command scheduler (the current one just allows the execution of one command at a time) and new i18n strings addition for the GUI option :-/ Changing to "wishlist" Kdevelop 3.2.0 CvsService command "Remove From Repository" should still visualize locally removed files on File Tree until these files are permanently removed from repository. If you right-click on a CVS file from File Tree -> CvsService -> Remove From Repository "cvs" will also remove local copy and kdevelop wrongly will also remove it from "File Tree". CVS locally removed file should remain on File Tree with "Locally Removed" shown status until it is permanently removed from CVS. Of course, that file is not permanently removed from repository (that is correct), but as Kdevelop has removed the file from File tree, there is no chance to commit from "File Tree" in order to remove the file permanently from repository. To do so, you have to commit manually the file from a shell or from another cvs application (cervisia, tkcvs, ...) to do so. This would be bad, because often removing a file in one place needs changes in other places as well and all those changes need to be comitted together. |