----Original Message----
>From: Christopher Cheng
>Sent: 13 September 2005 15:41
> Could somebody help me out?
>
>
>
> I am not sure whether the cvs file is corrupt or I have done something
> terribly wrong.
>
>
>
> Whenever I commit a file to the CVS, it increments a number after the
> revision number only
>
> For example,
>
> new revision: 1.22.2.1; previous revision: 1.22
>
>
>
> When I inspect the file in the server, I have the following. The head is
> definitely 1.23, but I am keep committing to 1.22 branches.
>
Then you probably have a sticky branch tag on the file - check with "cvs
status <filename>". You can use "cvs update -A <filename>" to get rid of
it; this will return your working directory copy to the trunk, merging
across any local changes that you have made. (But keep a copy of the file
just in case the merge goes awry; I don't think that -A makes a
.#filename.rev backup in the way that -C does).
cheers,
DaveK
--
Can't think of a witty .sigline today....
_______________________________________________
Info-cvs mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/info-cvs
