Scott Dudley writes:
>
> cvs server: sticky tag `v1-6' for file `altmedia/CHANGELOG' is not a
> branch
[...]
> there is no branch in this line of code. i've tagged each successive
> version v1-0, v1-1, etc. i checked it out using the following command:
>
> cvs co -r v1-6 altmedia
When you checkout a specific version like that, you can't commit changes
because there's no guarantee that the version you have is the most
recent version and, if it's not, CVS has no way to know where to put the
changes. If you want to make changes, you should either check out the
most recent version (by *NOT* using any -r option), or create a branch.
You can use ``cvs up -A'' in your working directory to remove the sticky
tag and update to the most recent version and then you'll be able to
commit your changes.
> after i commit, i tag the module. i've been doing things this way for
> weeks now without a glitch.
That seems excessive -- people usually commit much more often than they
tag. Typically, one commits when a particular (small) task is complete
and only tags when making a release.
-Larry Jones
Oh yeah? You just wait! -- Calvin
