Summary: | Creating subprojects does not give an option to 'Add to CVS' using cvs plugin | ||
---|---|---|---|
Product: | [Developer tools] kdevplatform | Reporter: | Jesse <jesse.y> |
Component: | cvs | Assignee: | KDevelop Developers <kdevelop-devel> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | gpiez |
Priority: | NOR | ||
Version: | 0.9.94 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Jesse
2003-08-29 16:20:01 UTC
*** Bug 62997 has been marked as a duplicate of this bug. *** It should be fixed with vcs/cvsservice: it no more bother the user about requesting to add files to a subproject which has not committed to repository yet. To commit a new subproject (and its dir) do as following (from file tree view): 1) select the subproject dir and rmb -> cvsservice -> add 2) select evey file in the subproject dir you want to add to repository and rmb-> cvsservice -> add 3) (while the files are still selected) rmb -> cvsservice -> commit 4) fill the dialog and have your files committed :-) Could be closed now? :-) The annoying part is fixed (I think) but the really confusing and bad usability part is not it seems (??) The whole point of the bug was to actually give a dialog of adding to the repository as soon as _any_ new directory gets created in your project -- this includes sub-projects which get handled as another directory. If it is not the case it not only requires the 4 (!) additional steps you noted but also this scenario: 1) You've added many directories off and on ... how do you know which has been added and have not? I don't think the vcscoloring handles that correct? And even if it did it would require _another_ step to "Sync with Repository" (can that be automated by the way so the user doesn't have to do it?) so you get the information you need. But thanks for the other fix :) That's still needed for directories that the user really didn't want in the repository As far as I can see this is fixed. Cvs unfortunately doesn't allow to do a recursive cvs add, so files have to be added individually. And kdevelop has no way to know wether a new subproject was created, so the automake manager would have to do a lot work for IMHO too little gain. |