Menu
▾
▴
#312 Graph is wrong in case of multiple symbolic branch names
Graph consider that a branch has a unique name but this
is wrong. In CVS, it is possible (via admin command) to
give more than one symbolic name to a branch (same as
for tags). Graph display all branches as separated
branches, even if symbolic names point to the same
branch. Graph should put in branch name box all branch
names of the CVS branch.
Logged In: YES
user_id=158827
How do you assign multiple branch names with the admin
command? Also, what would be the use of this?
So far I was only aware of import being able to cause this
kind of mess (it was fixed in more recent CVSNT builds).
Logged In: YES
user_id=544717
You can put a new branch name via admin command :
cvs admin -N[new_branch_tag]:[old_branch_tag]
This is usefull if you need to rename a branch but also need
to keep the old name for users still working on old branch
name, you need to keep the to names.
Even if this feature does not appear to be usefull to all,
it would ne nice to get a correct graph as having more than
one symbolic name for a branch is a reality and maybe
usefull when using CVS in an industrial environement.
Logged In: YES
user_id=119527
What exactly is "wrong" with the graph?
It looks fine for me - it shows new branch. True, it doesn't say
which one is symbolic but I am not sure I want it to. It would
be very confusing to have all names in one box actually.
Logged In: YES
user_id=544717
To understand, you must see a graph with non empty
branches (branches with some revision on it) and with 2 (or
more) same symbolic names; I have attached such exemple
or see it here : <img
src="http://www.nomblot.org/wincvs/branches.png"> /
http://www.nomblot.org/wincvs/branches.png .
Please, do have a look to this simple graph, and you will see
that you wound nether guess that :
Branch_A is in fact same as Branch_A _bis
Branch_B is in fact same as Branch_B_bis
Branch_C is in fact same as Branch_C_bis
Starting point are correct, as it would also be for tags, but
branches Branch_A ,Branch_B and Branch_C are not empy
branches, so graphic representation is really wrong :
Branch_A_bis ,Branch_B_bis and Branch_C_bis are not
empy branches.
Rcs log is : file :
Working file : 'thermometre.pyw'
Head revision : 1.1
Branch revision :
Locks : strict
Access :
Symbolic names :
1.1.0.6 : 'Branch_D'
1.1.2.2.0.2 : 'Branch_C_bis'
1.1.2.2.0.2 : 'Branch_C'
1.1.0.4 : 'Branch_B_bis'
1.1.0.4 : 'Branch_B'
1.1.0.2 : 'Branch_A_bis'
1.1.0.2 : 'Branch_A'
Keyword substitution : 'kv'
Total revisions : 7
Selected revisions : 7
Do not hesitate to contact me if you need more details.
Many thank's for trying to understand and fix this problem.
Logged In: YES
user_id=544717
to assign a second name to a branch, just use the very basci
standard cvs admin command :
cvs admin -NnewBranchName:OldBranchName
This is not a mess but a handsome CVS feature ery usefull
for groups heavily working with branches . This is for example
the possibilty to declare that for some files (a module
maybe) , the physical branche is the same than another one.
Minimum feature is to avoid breaking users worksapces while
renaming a branch. Reducing the little CVS possibilties with
branches does not sounds good to me ... even if CVS users
are not at ease with branches in general. This bug in WinCvs
Graph does not help them to understand branches !
Logged In: YES
user_id=119527
OK, I see what you mean. This will be more of a feature
request rather than bug.