Re: tkcvs : I can't see the details of the branch browser

Hello

With CVS repository, the Graphical Branch Diagram  for the file   README looks like the tkcvs_cvs.png.

Nevertheless, with the SVN repository, deduced from the CVS one by cvs2svn, the Graphical Branch Diagram  for the file   README looks like the tkcvs_svn.png.

I hoped that the two Graphical Branch Diagrams would give the same informations.

I hope the problem is easier to understand now.

Jerome

--- En date de : Mer 24.2.10, Michael Haggerty <[email protected]> a écrit :

De: Michael Haggerty <[email protected]>
Objet: Re: tkcvs : I can't see  the details of the branch browser
À: "jpt44svn" <[email protected]>
Cc: [email protected]
Date: Mercredi 24 février 2010, 12h47

jpt44svn wrote:
> I migrated a CVS repository to SVN with cvs2svn-2.3.0 with the following
> instruction :
> 
> $cvs2svn -s $depot_svn $depot_cvs --fs-type=fsfs
> --retain-conflicting-attic-files --username toto --default-eol=LF --encoding
> iso-8859-1
> 
> I use tkcvs-8.0.4 to see the evolutions of the files. It worked well with
> the CVS repository. It looked like :
> http://www.twobarleycorns.net/tkcvs/screen-branch.html
> 
> But with the new SVN repository (obtained with cvs2svn), it doesn't work. I
> only have the indication : trunk. All the previous tags do not appear.
> 
> Is there an cvs2svn option to concerv a appearance like
> http://www.twobarleycorns.net/tkcvs/screen-branch.html ?

I'm not familiar with tkcvs, but in general it is much harder for tools
to figure out which branches a file was copied to in Subversion than in
CVS.  It could be that this tool doesn't even try.

If you nevertheless think that the problem is with cvs2svn, then you
have to give us lower-level information, for example "I run command 'svn
log ...' and see FOO but I expected to see BAR."  Otherwise it is hard
to figure out which of the tools is to blame.

Michael

------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1670&dsMessageId=2451524

To unsubscribe from this discussion, e-mail: [[email protected]].