Re: Versioning modules instead of files?

[Sergei Organov]

Matthias Kaeppler <address@hidden> writes:

> Hi,
> 
> it seems that CVS is completely built around versioning individual files, such
> that every file has a revision number (which is perfectly fine, especially in
> later stages of development where the changes usually concentrate on a single
> few files).
> 
> 
> However, especially in early phases of development, revising single files is
> sort of too granular, because the changes are so huge.
> 
> It would be a lot better, if the versioning would happen on the module base,
> i.e. you can commit the content of your sandbox as a new version of your
> program rather than new versions of the individual files.
> 
> 
> Is that possible somehow? I can't find any means at all in the documentation
> to keep track and control the /program/ version instead of the individual
> source file revisions.

"cvs tag" is your friend:

<quote manual>
   Normally there is no reason to care about the revision numbers--it
is easier to treat them as internal numbers that CVS maintains, and tags
provide a better way to distinguish between things like release 1
versus release 2 of your product (*note Tags::).
</quote manual>


HTH

-- 
Sergei.