Bug 72467 - Creating a new class (c++) doesn't add it to the CVS
Summary: Creating a new class (c++) doesn't add it to the CVS
Status: RESOLVED WORKSFORME
Alias: None
Product: kdevplatform
Classification: Developer tools
Component: cvs (show other bugs)
Version: 0.9.94
Platform: Mandrake RPMs Linux
: NOR wishlist
Target Milestone: ---
Assignee: KDevelop Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-12 08:54 UTC by Fred Marmond
Modified: 2010-12-16 19:27 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fred Marmond 2004-01-12 08:54:01 UTC
Version:            (using KDE KDE 3.1.94)
Installed from:    Mandrake RPMs
OS:          Linux

For a project using CVS, created classes are not automatically added into the CVS repository. I have to add them by hand for each.

I think it is a bug (and not a feature request) as it is not the expected behavior. At least, for me, I would expect that the CVS is a kind of 'mirror' of my kdevelop project, so, adding something to the project would add it too in the CVS repository.
Comment 1 Amilcar do Carmo Lucas 2004-01-12 19:56:34 UTC
IMHO it is a feature request. Usually you need to explicitly add, and explicitly commit files with CVS.
Comment 2 Fred Marmond 2004-01-12 20:27:33 UTC
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
Comment 3 Jochen Wurster 2004-01-13 11:19:40 UTC
Having a look at the excellent cvs integration in eclipse might be a good idea.
Comment 4 Fred Marmond 2004-05-12 11:03:25 UTC
This had been implemented in a beta release.
Works, great!