-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Le Dimanche 6 Octobre 2002 21:05, Justin Ryan a écrit :
> Heya all..
>
> I've got a small project in CVS and am having some trouble. The problem
> is, when I try to add files to the project, although all other files are
> at revision 0.2.1.x, it adds files as revision 1.1.1.x.. When I try:
>
> cvs add apache.py
> cvs commit -r 0.2.1
>
> I get:
>
> cvs commit: cannot add file `apache.py' with revision `0.2.1'; must be
> on trunk
>
> what am I doing wrong?
A little help about how the revision number is currently managed in projects :
- Each file in project has an specific revision version. When you modify a
file and commit the file in repository, the tools (cvs in your case) update
the _file_ revision number.
- when you do a realease, you set a tag on all the project's files with a
unique number (the version of the software here, or doc :-) ... ). The tag
associate all the files revision number with the the unique number of your
software version. So you can had file with 1.1.1.1 (new one) and olders
files with number like 1.5.1.1 (example!!!), for the 0.9.0 revision off your
apps.
So don't confuse revision number of the project (tag) and revision number of
project 's files. The files revision number help you to know what files is
modified between released versions...
See the cvs manual and use of tag.
Jean-marc
PS : please forgive my poor english.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE9oJNSYilIC5+/QnYRAsBeAKCfuFBVvnOYwUMxJmGv+hlMb3V+eACfdghT
JSV7Da2VAyq/yoBH9tgkzoY=
=2YmS
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
