Yes, I'm sure that I checked out with 'buildXY-branch'.
The "cvs status -v" for one file in an affected directory shows following:
File: LSServers.sh Status: Up-to-date
Working revision: 1.22.6.1
Repository revision: 1.22.6.1 /home/cvs/lifesensor/Source/admin/LSServers.sh,v
Sticky Tag: build21-branch (branch: 1.22.6)
Sticky Date: (none)
Sticky Options: (none)
Existing Tags:
build21-branch (branch: 1.22.6)
build21 (revision: 1.22)
build20-branch (branch: 1.22.2)
build20 (revision: 1.22)
.....
I use WinCVS
Maik Walter
| "Jim.Hyslop"
<[EMAIL PROTECTED]>
12.04.2005 20:33 |
|
Maik Walter wrote:
> I use a SuSE SLES 9 server with CVS 1.11.14.
>
> After branching and new checkout for this new branch
> I have the strange effect that some directories from project
> have in their CVS/Tag file the entry "Nbranch-name" instead
> of "Tbranch-name".
> All files in the relevant directories have in CVS/Entries the
> right tag "Tbranch-name".
> Clear, consequence is adding or committing files in this
> directories not possible
> (cvs add: cannot add file on non-branch tag buildXY-branch).
>
> I did following for branching:
>
> cvs rtag buildXY project
> cvs rtag -b -r buildXY buildXY-branch project
>
> What could be the reason ?
Are you sure you have checked out 'buildXY-branch' and not 'buildXY'? What
does a 'cvs status -v' indicate (just pick one file, not all of them)?
What client are you using?
--
Jim Hyslop
Senior Software Designer
Leitch Technology International Inc. ( http://www.leitch.com )
Columnist, C/C++ Users Journal ( http://www.cuj.com/experts )
_______________________________________________ Info-cvs mailing list [email protected] http://lists.gnu.org/mailman/listinfo/info-cvs
