[GLLUG] Once more about Subversion

frank.dolinar at comcast.net frank.dolinar at comcast.net
Tue Feb 5 17:27:21 EST 2008


To all, again, thanks for the feedback.  It has helped and I've made some headway.  
That being said, I have some more questions.

1.  Given that the documentation indicates that revisions update the "revision number" for the entire trees...
and the documentation actually says:

Global Revision Numbers
Unlike most version control systems, Subversion's revision numbers apply to entire trees,
not individual files. Each revision number selects an entire tree, a particular state of the
repository after some committed change. Another way to think about it is that revision N
represents the state of the repository filesystem after the Nth commit. When Subversion
users talk about “revision 5 of foo.c”, they really mean “foo.c as it appears in revision
5.” Notice that in general, revisions N and M of a file do not necessarily differ! Many other
version control systems use per-file revision numbers, so this concept may seem unusual
at first. (Former CVS users might want to see Appendix B, Subversion for CVS Users for
more details.)

Are we talking about folders with sub structure or are we talking about the entire repository.


2.  I think I understand what a branch is at this point.  Under what circumstances would I want to create one?

3.  Related to question # 2, similar question about tags.

4.  The "MyProject" folder contains a .svn folder, a trunk folder, a branches folder, and a tags folder.   I'm placing my code files in the "MyProject" folder... except when I create a branch?  How do I make sure the code for the branch gets in the right location.  And related to question # 3, when and why do I associate a tag?


Yeah, I know I'm being a little dense about this.  But I want to get it right.

thanks again for all the help.

Frank




More information about the linux-user mailing list