[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Tue, 27 Mar 2001 12:08:23 +0200
I've noticed the following behaviour
on the "cvs co" command and I would
like to know if this is normal, and why.
I have the following situation in the
| 1.1 | Tagged with Head_vers_1_1
----> Branch br_1
There is, an initial version of all the
files which have been tagged with
Head_vers_1_1, and a branch on which some
developments have been made (and some
successive versions 188.8.131.52, 184.108.40.206, ...
are already available).
When I execute "cvs co" on all the repository,
I get the version on the main trunk, but
the tag Head_vers_1_1 is not available
(accessible to further cvs commands); moreover,
when I then have a look with "cvs status"
the tag appears in the list of existing
tags and not as a sticky tag.
If I then do "cvs co -r Head_vers_1_1",
everything works fine: the tag Head_vers_1_1
is recognized, and "cvs status" prints
it as a sticky tag.
My questions then are the following:
- is that normal that tag Head_vers_1_1
- is that normal that "cvs co" is equivalent
with "cvs co -A"? (I would have expected
that "cvs co" gets the final version on
the trunk, with all the associated tags).
The branch br_1 has been created after
the 1.1 on the main trunk has been tagged
with Head_vers_1_1, and further developments
on the branch have created new files that
were not initially in the repository. Can
this be the reason why tag Head_vers_1_1
has become sticky?
(the question why "cvs co" <=> "cvs co -A"
remains still open even in this case)
Thanks a lot again for any suggestion,
Functional Verification Center of Competence - CMG
STMicroelectronics, 9 chem de la Dhuy, 38240 MEYLAN, FRANCE
Phone: (+33) (0)4 76 58 68 90, Fax: (+33) (0)4 76 58 40 11
- CVS Checkout, Jouni Kylä-Nikkilä, 2001/03/09
- cvs checkout,
irina sturm <=