Summary: | Creating a new class (c++) doesn't add it to the CVS | ||
---|---|---|---|
Product: | [Developer tools] kdevplatform | Reporter: | Fred Marmond <fmarmond> |
Component: | cvs | Assignee: | KDevelop Developers <kdevelop-devel> |
Status: | RESOLVED WORKSFORME | ||
Severity: | wishlist | ||
Priority: | NOR | ||
Version: | 0.9.94 | ||
Target Milestone: | --- | ||
Platform: | Mandrake RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Fred Marmond
2004-01-12 08:54:01 UTC
IMHO it is a feature request. Usually you need to explicitly add, and explicitly commit files with CVS. I agree with explicitly commit files. But adding them one by one is a very annoying thing. May I suggest a compromise? Perhaps (a real feature request) a file diff between the kDevelop project and the cvs(or whatever else) repository may be a good thing. This may only show filenames, and a tag to indicate if file contain differences. With that, we could see what which files are in the project and not in the cvs repository, and what files are changed. Then, we could make a 'cvs' diff to see real differences. I would find that very usefull when creating a new part of a project: we could concentrate on the code itself, and not in the versionning in a first time. When the part is done, (creating new files, deleting just created, re-creating...), we could make a kproj/cvs diff, and click on files signaled as 'new to repository' to add them into the CVS, and then, make our commits. Fred Having a look at the excellent cvs integration in eclipse might be a good idea. This had been implemented in a beta release. Works, great! |