Trouble with RevisionNames

SteffenNetz
SteffenNetz
Hello,    I'm just getting into SVN from CVS. I'm especially confused with  the names of revisions.  Let's say, my Repository looks like that:  test/   trunk/   test.c   pgm/   test.c   timing.ctlf   branch/   tags/   Test/   test.c   pgm/   test.c   timing.ctlf    I've successfully tagged my Project to tags/Test    In cvs i would write in my trunk-Workingcopy (rather easy and short):  cvs diff -r ZMD test.c    How would this be in SubVersion?  The only one, I've found is  svn diff file:///home/digital/netz/svn/test/tags/Test file:///home/digital/netz/svn/test/trunk    Is there any abbrevation for this long names?    On the other hand, I would diff my local copy:  svn diff file:///home/digital/netz/svn/test/tags/Test/test.c test.c  svn: Target lists to diff may not contain both working copy paths and URLs    Why not, how I get the difference between my working copy and a Tag?    What about URL, RevisionNames,Local and so on?    I'm very confused, please give me some advice. :(    Thank you very much,  Steffen

Last updated

k-dub
k-dub
I can't answer your question, but I have some advise. If you don't want it, stop reading now.    I've seen the trouble skilled CVS users have with Subversion. I don't know if I was "skilled", but I had my share of trouble. The best solution for myself and every CVS convert I've talked to is this: forget CVS. Let me explain.    One of Subversion's goals was to be close in syntax and an easy replacement for CVS. One downfall is that Subversion is the design is advanced enough that accomplishing task A is not handled exactly the same way. It's best, IMHO, to take a deep breath and go read the Subversion documentation from front to back, working through every example. Pretty soon, the CVS similarities will begin to link themselves together in your brain, like a Wiki. This is a much smoother transition path than trying to create mental translations from CVS to svn.    The people I've met who haven't used CVS in the past just take the Subversion instructions at face value and have an easier time, so I'm convinced that attempting to apply CVS skills to Subversion is a problem for most people.    Sorry I couldn't answer your question directly, but I've forgotten almost everything about CVS except the bare minimum to get by on Sourceforge.    Hope that helps!

1-2 of 2

Reply to this discussion

You cannot edit posts or make replies: You should be logged in before you can post.